T5733: Better CUDA Support

Aetf noreply at phabricator.kde.org
Thu Mar 23 19:39:40 UTC 2017


qi437103 added a comment.


  Sorry I misread the last comment. No it's not affected by `nostdinc` or `nostdinc++`, as in current code those are not added to the command line.
  
  After played with the command line directly, I find there might be more complex issues if we have to exclude standard includes.
  
  - `clang --cuda-path=/opt/cuda -std=c++11 -nostdinc -nostdinc++ -xcuda -isystem/usr/include/c++/6.3.1 -isystem/usr/include/c++/6.3.1/x86_64-pc-linux-gnu -isystem/usr/include/c++/6.3.1/backward -isystem/usr/local/include -isystem/usr/lib/clang/3.9.1/include -isystem/usr/include -imacros /home/aetf/definestest_files-clang.J25682 /home/aetf/develop/vcs/kdevelop/languages/clang/tests/files/cuda.cu`
  
  gives various undeclared identifier errors for clang 3.9 and 4.0
  
  - `clang --cuda-path=/opt/cuda -std=c++11 -nostdinc++ -xcuda -isystem/usr/include/c++/6.3.1 -isystem/usr/include/c++/6.3.1/x86_64-pc-linux-gnu -isystem/usr/include/c++/6.3.1/backward -isystem/usr/local/include -isystem/usr/include -imacros /home/aetf/definestest_files-clang.J25682 /home/aetf/develop/vcs/kdevelop/languages/clang/tests/files/cuda.cu`
  
  Removing `-nostdinc` and `-isystem/usr/lib/clang/3.9.1/include` makes it work well for clang 4.0 but generates the same error for clang 3.9
  
  - Whatever other arguemts passed in, `nocudainc` will make it generate errors about undefined cuda keywords.

TASK DETAIL
  https://phabricator.kde.org/T5733

To: qi437103
Cc: mwolff, kfunk, kdevelop-devel, #kdevelop, qi437103, geetamc, Pilzschaf, akshaydeo, surgenight, arrowdodger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170323/d2e10726/attachment-0001.html>


More information about the KDevelop-devel mailing list