Maintain separate flags for C++ compiler invocations
Previously we would pass flags intended for the C compiler to the C++ compiler (see #16738). This would cause, for instance, `-std=gnu99` to be passed to the C++ compiler, causing spurious test failures. Fix this by maintaining a separate set of flags for C++ compilation invocations.
Showing
- aclocal.m4 3 additions, 0 deletionsaclocal.m4
- compiler/ghci/Linker.hs 1 addition, 1 deletioncompiler/ghci/Linker.hs
- compiler/main/DynFlags.hs 2 additions, 2 deletionscompiler/main/DynFlags.hs
- compiler/main/Settings.hs 1 addition, 1 deletioncompiler/main/Settings.hs
- compiler/main/SysTools.hs 17 additions, 16 deletionscompiler/main/SysTools.hs
- compiler/main/SysTools/Info.hs 1 addition, 1 deletioncompiler/main/SysTools/Info.hs
- compiler/main/SysTools/Tasks.hs 16 additions, 12 deletionscompiler/main/SysTools/Tasks.hs
- compiler/main/ToolSettings.hs 1 addition, 1 deletioncompiler/main/ToolSettings.hs
- hadrian/cfg/system.config.in 1 addition, 0 deletionshadrian/cfg/system.config.in
- hadrian/src/Oracles/Setting.hs 2 additions, 0 deletionshadrian/src/Oracles/Setting.hs
- hadrian/src/Rules/Generate.hs 1 addition, 0 deletionshadrian/src/Rules/Generate.hs
- includes/ghc.mk 1 addition, 0 deletionsincludes/ghc.mk
- mk/config.mk.in 1 addition, 0 deletionsmk/config.mk.in
Loading
Please register or sign in to comment