#
1.6 |
|
11-Nov-2023 |
robert |
merge clang-16.0.6
|
Revision tags: OPENBSD_7_1_BASE OPENBSD_7_2_BASE OPENBSD_7_3_BASE OPENBSD_7_4_BASE
|
#
1.5 |
|
17-Dec-2021 |
patrick |
Merge LLVM 13.0.0.
|
Revision tags: OPENBSD_7_0_BASE
|
#
1.4 |
|
28-Apr-2021 |
patrick |
Merge LLVM 11.1.0.
|
Revision tags: OPENBSD_6_9_BASE
|
#
1.3 |
|
06-Feb-2021 |
naddy |
switch clang to -fno-common by default
Common variables will be flagged as errors by default. This can be overridden with -fcommon.
Cherry-pick this change that will be part of LLVM11. We bring it forward so we can finish fixing the fallout in the ports tree.
ok deraadt@ sthen@ mglocker@
|
Revision tags: OPENBSD_6_8_BASE
|
#
1.2 |
|
10-Sep-2020 |
gkoehler |
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
|
#
1.1 |
|
03-Aug-2020 |
patrick |
branches: 1.1.1; Initial revision
|
#
1.5 |
|
17-Dec-2021 |
patrick |
Merge LLVM 13.0.0.
|
Revision tags: OPENBSD_7_0_BASE
|
#
1.4 |
|
28-Apr-2021 |
patrick |
Merge LLVM 11.1.0.
|
Revision tags: OPENBSD_6_9_BASE
|
#
1.3 |
|
06-Feb-2021 |
naddy |
switch clang to -fno-common by default
Common variables will be flagged as errors by default. This can be overridden with -fcommon.
Cherry-pick this change that will be part of LLVM11. We bring it forward so we can finish fixing the fallout in the ports tree.
ok deraadt@ sthen@ mglocker@
|
Revision tags: OPENBSD_6_8_BASE
|
#
1.2 |
|
10-Sep-2020 |
gkoehler |
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
|
#
1.1 |
|
03-Aug-2020 |
patrick |
branches: 1.1.1; Initial revision
|
#
1.4 |
|
28-Apr-2021 |
patrick |
Merge LLVM 11.1.0.
|
Revision tags: OPENBSD_6_9_BASE
|
#
1.3 |
|
06-Feb-2021 |
naddy |
switch clang to -fno-common by default
Common variables will be flagged as errors by default. This can be overridden with -fcommon.
Cherry-pick this change that will be part of LLVM11. We bring it forward so we can finish fixing the fallout in the ports tree.
ok deraadt@ sthen@ mglocker@
|
Revision tags: OPENBSD_6_8_BASE
|
#
1.2 |
|
10-Sep-2020 |
gkoehler |
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
|
#
1.1 |
|
03-Aug-2020 |
patrick |
branches: 1.1.1; Initial revision
|
#
1.3 |
|
06-Feb-2021 |
naddy |
switch clang to -fno-common by default
Common variables will be flagged as errors by default. This can be overridden with -fcommon.
Cherry-pick this change that will be part of LLVM11. We bring it forward so we can finish fixing the fallout in the ports tree.
ok deraadt@ sthen@ mglocker@
|
Revision tags: OPENBSD_6_8_BASE
|
#
1.2 |
|
10-Sep-2020 |
gkoehler |
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
|
#
1.1 |
|
03-Aug-2020 |
patrick |
branches: 1.1.1; Initial revision
|
#
1.2 |
|
10-Sep-2020 |
gkoehler |
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
|
#
1.1 |
|
03-Aug-2020 |
patrick |
branches: 1.1.1; Initial revision
|
Revision tags: CLANG_10_0_0
|
#
1.1.1.1 |
|
03-Aug-2020 |
patrick |
Import LLVM 10.0.0 release including clang, lld and lldb.
ok hackroom tested by plenty
|