You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clang 8.0 introduced a better "escape hatch" for clang-cl than -Xclang: /clang:ARG. The former passes the argument directly to cc1; the latter passes the argument to the clang driver itself, essentially allowing anything to be passed through as if you were using clang instead of clang-cl.
I think this is just a matter of adding a SlashClang case to ArgData and adding similar reprocessing of SlashClang arguments as the XClang case already does. But it'd be nice to not completely duplicate the XClang processing code.
The text was updated successfully, but these errors were encountered:
clang 8.0 introduced a better "escape hatch" for
clang-cl
than-Xclang
:/clang:ARG
. The former passes the argument directly tocc1
; the latter passes the argument to the clang driver itself, essentially allowing anything to be passed through as if you were usingclang
instead ofclang-cl
.I think this is just a matter of adding a
SlashClang
case toArgData
and adding similar reprocessing ofSlashClang
arguments as theXClang
case already does. But it'd be nice to not completely duplicate theXClang
processing code.The text was updated successfully, but these errors were encountered: