22 Jan
2014
22 Jan
'14
5:28 a.m.
On Wed, Jan 22, 2014 at 3:30 AM, Mathias Gaunard
Hi,
I noticed that I had some problems with some nvcc (NVIDIA CUDA) versions and BOOST_NOINLINE.
The logic for defining BOOST_NOINLINE seems to be the same as that of BOOST_FORCEINLINE, which does work correctly, so it seems to be a nvcc bug that's not fully compatible with GCC despite claiming to be.
What would be the correct way to fix that?
I suppose, you could just add: #define BOOST_NOINLINE to boost/config/compiler/nvcc.hpp, with a descriptive comment. When the macro is defined in the compiler's config, it won't be defined by suffix.hpp. How does the problem manifest itself though?