Boost C++ Libraries: Ticket #8647: Incorrect Identification of CUDA NVCC with User-Defined Backend

attachment set

ryo-nishimura@… — Tue, 04 Jun 2013 07:18:26 GMT

attachment → nvcc.hpp.patch

component changed; owner set

viboes — Sat, 08 Jun 2013 16:53:47 GMT

owner set to John Maddock
component None → config

John Maddock — Tue, 23 Jul 2013 17:44:01 GMT

I'm wondering - since nvcc.hpp basically does next to nothing - whether it would be better to simply remove it, and let select_compiler_config.hpp select on the basis of the underlying compiler?

attachment set

ryo-nishimura@… — Wed, 24 Jul 2013 04:53:49 GMT

attachment → nvcc.hpp.johnmaddock.patch

ryo-nishimura@… — Wed, 24 Jul 2013 04:59:01 GMT

johnmaddock, thank you for your advising. I have revised the patch with your concept.

My new patch is to make the NVCC compiler's branch of select_compiler_config.hpp independent from the other compilers' tree and to remove the existing duplicated tree of nvcc.hpp.

I have checked this patch working fine as the old patch. Would it become a more smart solution for my purpose?

status changed; resolution set

John Maddock — Wed, 24 Jul 2013 17:19:06 GMT

status new → closed
resolution → fixed

(In [85154]) Apply patch from #8647. Fixes #8647.

robert.maynard@… — Wed, 15 Jan 2014 21:46:18 GMT

I apologize if it is bad behavior to comment on closed bugs.

These changes to detecting the backend for nvcc has had the side effect of making it not possible to use the clang backend with CUDA 5.5. My testbed machine is a Mac Lion with CUDA 5.5 and XCode 5.0.2.

The problem is that the nvcc with the clang backend is expecting clang to be emulating gcc 4.2.

The solution is that select_compiler_config.hpp should have the following guard:

#elif defined __clang__ && !defined(__CUDACC__)
//  Clang C++ emulates GCC, so it has to appear early.
#   define BOOST_COMPILER_CONFIG "boost/config/compiler/clang.hpp"

ryo-nishimura@… — Thu, 16 Jan 2014 01:29:23 GMT

Hi Robert Maynard,

Thank you for your reporting a bug of my patch.

The user-defined backend trouble I really had was on Linux, and CUDA 5.5 on OS X was used as only my sophism in order to persuade necessity of my patch. Really I have never understood nor tested the implementation of OS X CUDA 5.5 released after my patch committed.

I apologize for my irresponsible and thank you again.