[petsc-dev] Is there a good reason that BuildSystem's cuda.py requires GNU compilers?

Mills, Richard Tran rtmills at anl.gov
Wed Mar 13 00:14:48 CDT 2019

Jed, yes, I'm on petsc-maint and I see this thread now. Thanks; I'll take a look. (I've had a crazy day and have been more behind than usual on email.)


On 3/12/19 8:48 PM, Jed Brown wrote:

Richard, are you not on petsc-maint?  There was a thread about this today.

PGI "community edition" is free now.  We could add it to our test suite.


"Smith, Barry F. via petsc-dev" <petsc-dev at mcs.anl.gov><mailto:petsc-dev at mcs.anl.gov> writes:


    You need to remove the isGNU() test and then experiment with getting the Nvidia tools to use the compiler you want it to use.

     No one has made a serious effort to use any other compilers but Gnu (at least not publicly).


On Mar 12, 2019, at 10:40 PM, Mills, Richard Tran via petsc-dev <petsc-dev at mcs.anl.gov><mailto:petsc-dev at mcs.anl.gov> wrote:

Fellow PETSc developers,

If I try to configure PETSc with CUDA support on the ORNL Summit system using non-GNU compilers, I run into an error due to the following code in packages/cuda.py:

  def configureTypes(self):
    import config.setCompilers
    if not config.setCompilers.Configure.isGNU(self.setCompilers.CC, self.log):
      raise RuntimeError('Must use GNU compilers with CUDA')

Is this just because this code predates support for other host compilers with nvcc, or is there perhaps some more subtle reason that I, with my inexperience using CUDA, don't know about? I'm guessing that I just need to add support for using '-ccbin' appropriately to set the location of the non-GNU host compiler, but maybe there is something that I'm missing. I poked around in the petsc-dev mailing list archives and can find a few old threads on using non-GNU compilers, but I'm not sure what conclusions were reached.

Best regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190313/47e785ed/attachment-0001.html>

More information about the petsc-dev mailing list