diff options
| author | Palmer Dabbelt <palmer@rivosinc.com> | 2022-09-09 02:46:40 -0700 |
|---|---|---|
| committer | Palmer Dabbelt <palmer@rivosinc.com> | 2022-09-30 15:24:12 -0700 |
| commit | 4dcd340ebaae8213eeae89894b5ecdf61b0eb100 (patch) | |
| tree | 3a158e0701af982bdb2a9ce160ebffd82af47985 /gcc | |
| parent | 75c0899493cd84e64bd30210e848d0d1e9979494 (diff) | |
| download | gcc-4dcd340ebaae8213eeae89894b5ecdf61b0eb100.zip gcc-4dcd340ebaae8213eeae89894b5ecdf61b0eb100.tar.gz gcc-4dcd340ebaae8213eeae89894b5ecdf61b0eb100.tar.bz2 | |
Document -fexcess-precision=16 in tm.texi
I just happened to stuble on this one while trying to sort out the
RISC-V bits.
gcc/ChangeLog
* doc/tm.texi (TARGET_C_EXCESS_PRECISION): Add 16.
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/doc/tm.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index 858bfb8..7590924 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -1009,7 +1009,7 @@ of the excess precision explicitly added. For @code{EXCESS_PRECISION_TYPE_FLOAT16}, and @code{EXCESS_PRECISION_TYPE_FAST}, the target should return the explicit excess precision that should be added depending on the -value set for @option{-fexcess-precision=@r{[}standard@r{|}fast@r{]}}. +value set for @option{-fexcess-precision=@r{[}standard@r{|}fast@r{|}16@r{]}}. Note that unpredictable explicit excess precision does not make sense, so a target should never return @code{FLT_EVAL_METHOD_UNPREDICTABLE} when @var{type} is @code{EXCESS_PRECISION_TYPE_STANDARD}, |