You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: clang/docs/UsersManual.rst
-20Lines changed: 0 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1478,26 +1478,6 @@ Note that floating-point operations performed as part of constant initialization
1478
1478
* ``maytrap`` The compiler avoids transformations that may raise exceptions that would not have been raised by the original code. Constant folding performed by the compiler is exempt from this option.
1479
1479
* ``strict`` The compiler ensures that all transformations strictly preserve the floating point exception semantics of the original code.
1480
1480
1481
-
.. option:: -f[no-]protect-parens:
1482
-
1483
-
This option pertains to floating-point types, complex types with
1484
-
floating-point components, and vectors of these types. Some arithmetic
1485
-
expression transformations that are mathematically correct and permissible
1486
-
according to the C and C++ language standards may be incorrect when dealing
1487
-
with floating-point types, such as reassociation and distribution. Further,
1488
-
the optimizer may ignore parentheses when computing arithmetic expressions
1489
-
in circumstances where the parenthesized and unparenthesized expression
1490
-
express the same mathematical value. For example (a+b)+c is the same
1491
-
mathematical value as a+(b+c), but the optimizer is free to evaluate the
1492
-
additions in any order regardless of the parentheses. When enabled, this
1493
-
option forces the optimizer to honor the order of operations with respect
1494
-
to parentheses in all circumstances.
1495
-
1496
-
Note that floating-point contraction (option `-ffp-contract=`) is disabled
1497
-
when `-fprotect-parens` is enabled. Also note that in safe floating-point
1498
-
modes, such as `-ffp-model=precise` or `-ffp-model=strict`, this option
1499
-
has no effect because the optimizer is prohibited from making unsafe
0 commit comments