mirror of
https://github.com/llvm/llvm-project.git
synced 2025-05-03 20:26:06 +00:00

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
17 lines
946 B
C++
17 lines
946 B
C++
// RUN: %clang_cc1 -triple mips64-linux-gnu -frounding-math -ffp-exception-behavior=strict -O2 -verify=rounding,exception -emit-llvm -o - %s | FileCheck %s
|
|
// RUN: %clang_cc1 -triple mips64-linux-gnu -ffp-exception-behavior=strict -O2 -verify=exception -emit-llvm -o - %s | FileCheck %s
|
|
// RUN: %clang_cc1 -triple mips64-linux-gnu -frounding-math -O2 -verify=rounding -emit-llvm -o - %s | FileCheck %s
|
|
//
|
|
// Verify that constrained intrinsics are not used.
|
|
// As more targets gain support for constrained intrinsics the triple
|
|
// in this test will need to change.
|
|
|
|
// rounding-warning@* {{overriding currently unsupported rounding mode on this target}}
|
|
// exception-warning@* {{overriding currently unsupported use of floating point exceptions on this target}}
|
|
float fp_precise_1(float a, float b, float c) {
|
|
// CHECK: define float @_Z12fp_precise_1fff
|
|
// CHECK: %[[M:.+]] = fmul float{{.*}}
|
|
// CHECK: fadd float %[[M]], %c
|
|
return a * b + c;
|
|
}
|