[petsc-dev] Intel compilers + CUDA

John Fettig john.fettig at gmail.com
Fri Feb 24 11:26:31 CST 2012


On Fri, Feb 24, 2012 at 12:12 PM, Matthew Knepley <knepley at gmail.com> wrote:

> On Fri, Feb 24, 2012 at 11:06 AM, John Fettig <john.fettig at gmail.com>wrote:
>
>> On Fri, Feb 24, 2012 at 11:56 AM, Satish Balay <balay at mcs.anl.gov> wrote:
>>
>>> for one I mistyped the option - it should be: --with-cudac='nvcc -ccbin
>>> icc'
>>>
>>> But then - should it not be c++? [as cuda internally uses g++ - not
>>> gcc]. So
>>>
>>> --with-cudac='nvcc -ccbin icpc'.
>>>
>>> But this gives me all kinds of wierd errors in configure.log.. Maybe
>>> it won't work [with intel compilers]..
>>>
>>
>> CUDA .cu files are written in C with some extensions (that are handled by
>> nvcc and not the passed compiler), so I think you have to use a C
>> compiler.  You can't write C++ in a .cu file.
>>
>
> I do not think this is correct. You can have C++.
>

Oops, you are right.  There are restrictions on what can be on the device
side, but not on the host side.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120224/f17aeed4/attachment.html>


More information about the petsc-dev mailing list