merge clang-16.0.6
import of clang from LLVM-16.0.6
Our malloc(3) guarantees 16-byte alignment.ok sthen@, tb@
Merge LLVM 13.0.0.
Import LLVM 13.0.0 release.
Pull in support from a future clang for __GCC_HAVE_SYNC_COMPARE_AND_SWAP_xdefines because we need it nowfrom https://reviews.llvm.org/D91784ok mlarkin kettenis
Merge LLVM 11.1.0.
Import LLVM 11.1.0 release including clang, lld and lldb.
Disable strict floating point if not X86Disable options like clang -fno-unsafe-math-optimizations for alltargets except X86 (and SystemZ). This prevents a crash of clang,reported by cwen@, in gr
Disable strict floating point if not X86Disable options like clang -fno-unsafe-math-optimizations for alltargets 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/d4ce862Reland "[FPEnv][Clang][Driver] Disable constrained floating point on targets lacking support."We currently have strict floating point/constrained floating point enabledfor all targets. Constrained SDAG nodes get converted to the regular onesbefore reaching the target layer. In theory this should be fine.However, the changes are exposed to users through multiple clang optionsalready 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 everywhereexcept X86 and SystemZ. A warning will be printed when this happens.Use the new -fexperimental-strict-floating-point flag to force allowingstrict floating point on hosts that aren't already marked as supportingit (X86 and SystemZ).Differential Revision: https://reviews.llvm.org/D80952
show more ...
Import LLVM 10.0.1 including clang, lld and lldb.
Import LLVM 10.0.0 release including clang, lld and lldb.ok hackroomtested by plenty