CVSROOT: /cvs
Module name: src
Changes by: [email protected] 2020/09/10 14:28:14
Modified files:
gnu/llvm/clang/docs: ClangCommandLineReference.rst
gnu/llvm/clang/include/clang/Basic: CodeGenOptions.def
DiagnosticFrontendKinds.td
DiagnosticGroups.td
LangOptions.def TargetInfo.h
gnu/llvm/clang/include/clang/Driver: Options.td
gnu/llvm/clang/lib/Basic: TargetInfo.cpp
gnu/llvm/clang/lib/Basic/Targets: SystemZ.h X86.h
gnu/llvm/clang/lib/Frontend: CompilerInstance.cpp
CompilerInvocation.cpp
Log message:
Disable strict floating point if not X86
Disable options like clang -fno-unsafe-math-optimizations for all
targets except X86 (and SystemZ). This prevents a crash of clang,
reported by cwen@, in graphics/babl or emulators/mednafen for powerpc.
ok mortimer@
This change comes from llvm 11.x:
https://github.com/llvm/llvm-project/commit/d4ce862
Reland "[FPEnv][Clang][Driver] Disable constrained floating point on targets
lacking support."
We currently have strict floating point/constrained floating point enabled
for all targets. Constrained SDAG nodes get converted to the regular ones
before reaching the target layer. In theory this should be fine.
However, the changes are exposed to users through multiple clang options
already in use in the field, and the changes are _completely_ _untested_
on almost all of our targets. Bugs have already been found, like
"https://bugs.llvm.org/show_bug.cgi?id=45274";.
This patch disables constrained floating point options in clang everywhere
except X86 and SystemZ. A warning will be printed when this happens.
Use the new -fexperimental-strict-floating-point flag to force allowing
strict floating point on hosts that aren't already marked as supporting
it (X86 and SystemZ).
Differential Revision: https://reviews.llvm.org/D80952
