Comments (5)
Here's a minimal example that causes compilation errors. Save as .cu
or .cpp
file, compile with nvcc.exe
or cl.exe
with the libcu++ includes.
#include <cuda/std/atomic>
struct A {
float near;
float far;
};
int main() { }
from libcudacxx.
The libcu++ version is the one included with CUDA 11.2.
cl.exe version:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
nvcc.exe version:
Cuda compilation tools, release 11.2, V11.2.67
from libcudacxx.
Unfortunately there is nothing we can do here.
from libcudacxx.
Would #undef
s for near
and far
after "windef.h" includes inside libcu++ not be a workable fix?
from libcudacxx.
We cannot #undef macros from a system header.
While at the moment the macro might be useless it could get some meaning in the future leading to havoc
from libcudacxx.
Related Issues (20)
- [QUESTION] Can we remove the `isnan` check in the `complex<T>` multiplication operator? HOT 6
- [Question] understanding documentation of cuda::atomic::atomic_thread_fence HOT 2
- CUDA Tuple Structured Binding Declaration Broken HOT 4
- libcu++ should document policy for mixing a custom version with the CUDA Toolkit HOT 2
- `error: "cuda::std::cuda" is ambiguous` when including <cuda/std> HOT 6
- Issue with cuda::atomic_ref::notify_one and wait HOT 1
- Feature request: fp32 multiplication with zero optimization specifier HOT 5
- Copyright in `nv` files HOT 2
- A device variable cannot be marked constexpr (cuda::std::swap / CTK 11.2) HOT 2
- `proclaim_return_type` and `__invoke` should be decorated with `nv_exec_check_disable` HOT 2
- Add `cuda::std::expected`
- Placement new creates performance issues
- libcu++ should not define __host__/__device__/__forceinline__ (or any other runtime macros) HOT 2
- atomic fence questions HOT 2
- Hide if target bits from NVCC/NVRTC
- Function objects in `<functional>` need to be annotated with `nv_exec_check_disable` HOT 1
- Does `cuda::std::complex` have opt-in for simplified complex math HOT 3
- libcu++ should build with gcc-6
- Passing `cuda::proclaim_return_type` to `thrust::make_transform_iterator` gives compilation error HOT 1
- Support fixed-width floating point types
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from libcudacxx.