Turns out the variadic function checking added in r258643 was too strict
for some existing users; give them an escape valve. When
-fcuda-allow-variadic-functions is passed, the front-end makes no
attempt to disallow C-style variadic functions. Calls to va_arg are
still not allowed.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
cfe/trunk/include/clang/Driver/CC1Options.td | ||
---|---|---|
681 | AFAICT, these are customer facing flags, correct? If so, shouldn't these options be hidden from the help (via the HelpHidden flag AFAICT)? |
cfe/trunk/include/clang/Driver/CC1Options.td | ||
---|---|---|
681 | This might cause issues such as those reported in PR26317 and PR26318. |
cfe/trunk/include/clang/Driver/CC1Options.td | ||
---|---|---|
681 | These are cc1-only options and do *not* show up in top-level --help. |
cfe/trunk/include/clang/Driver/CC1Options.td | ||
---|---|---|
681 | Ah, yes. You are correct. |
Could you please add this to the documentation?
Could this be made the default? It seems like nvcc does this by default.
Clang already does that, though we only allow variadic functions that don't actually use the vararg arguments: https://reviews.llvm.org/D151359
It's sufficient to compile recent CUDA/libcu++ headers w/o errors.
AFAICT, these are customer facing flags, correct? If so, shouldn't these options be hidden from the help (via the HelpHidden flag AFAICT)?