RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-25 20:39:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

[NFC][LangRef][FPEnv] Fix whitespace for denormal-fp-math/denormal-fp-math-f32

Browse Source 
Fix incorrect spacing for `denormal-fp-math` and `denormal-fp-math-f32`. No
other changes.
This commit is contained in:
Cameron McInally 2020-02-04 11:10:43 -06:00
parent aa49707128
commit 1f64f59a06
1 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
docs/LangRef.rst
View File

@ -1820,27 +1820,27 @@ example:
not introduce any new floating-point instructions that may trap.
``"denormal-fp-math"``
This indicates the denormal (subnormal) handling that may be assumed
for the default floating-point environment. This may be one of
``"ieee"``, ``"preserve-sign"``, or ``"positive-zero"``. If this
is attribute is not specified, the default is ``"ieee"``. If the
mode is ``"preserve-sign"``, or ``"positive-zero"``, denormal
outputs may be flushed to zero by standard floating point
operations. It is not mandated that flushing to zero occurs, but if
a denormal output is flushed to zero, it must respect the sign
mode. Not all targets support all modes. While this indicates the
expected floating point mode the function will be executed with,
this does not make any attempt to ensure the mode is
consistent. User or platform code is expected to set the floating
point mode appropriately before function entry.
This indicates the denormal (subnormal) handling that may be assumed
for the default floating-point environment. This may be one of
``"ieee"``, ``"preserve-sign"``, or ``"positive-zero"``. If this
is attribute is not specified, the default is ``"ieee"``. If the
mode is ``"preserve-sign"``, or ``"positive-zero"``, denormal
outputs may be flushed to zero by standard floating point
operations. It is not mandated that flushing to zero occurs, but if
a denormal output is flushed to zero, it must respect the sign
mode. Not all targets support all modes. While this indicates the
expected floating point mode the function will be executed with,
this does not make any attempt to ensure the mode is
consistent. User or platform code is expected to set the floating
point mode appropriately before function entry.
``"denormal-fp-math-f32"``
Same as ``"denormal-fp-math"``, but only controls the behavior of
the 32-bit float type (or vectors of 32-bit floats). If both are
are present, this overrides ``"denormal-fp-math"``. Not all targets
support separately setting the denormal mode per type, and no
attempt is made to diagnose unsupported uses. Currently this
attribute is respected by the AMDGPU and NVPTX backends.
Same as ``"denormal-fp-math"``, but only controls the behavior of
the 32-bit float type (or vectors of 32-bit floats). If both are
are present, this overrides ``"denormal-fp-math"``. Not all targets
support separately setting the denormal mode per type, and no
attempt is made to diagnose unsupported uses. Currently this
attribute is respected by the AMDGPU and NVPTX backends.
``"thunk"``
This attribute indicates that the function will delegate to some other