diff options
| author | Artem Belevich <tra@google.com> | 2020-12-04 11:27:39 -0800 |
|---|---|---|
| committer | Artem Belevich <tra@google.com> | 2020-12-04 12:03:35 -0800 |
| commit | 43267929423bf768bbbcc65e47a07e37af7f4e22 (patch) | |
| tree | d3fbfeeb6678704366a6e795ce8a91c23deccd0b /clang/lib/Tooling/JSONCompilationDatabase.cpp | |
| parent | 4b5dc150b9862271720b3d56a3e723a55dd81838 (diff) | |
| download | llvm-43267929423bf768bbbcc65e47a07e37af7f4e22.zip llvm-43267929423bf768bbbcc65e47a07e37af7f4e22.tar.gz llvm-43267929423bf768bbbcc65e47a07e37af7f4e22.tar.bz2 | |
[CUDA] Another attempt to fix early inclusion of <new> from libstdc++
Previous patch (9a465057a64dba) did not fix the problem.
https://bugs.llvm.org/show_bug.cgi?id=48228
If the <new> is included too early, before CUDA-specific defines are available,
just include-next the standard <new> and undo the include guard. CUDA-specific
variants of operator new/delete will be declared if/when <new> is used from the
CUDA source itself, when all CUDA-related macros are available.
Differential Revision: https://reviews.llvm.org/D91807
Diffstat (limited to 'clang/lib/Tooling/JSONCompilationDatabase.cpp')
0 files changed, 0 insertions, 0 deletions