public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-3001] Document -fexcess-precision=16 in tm.texi
@ 2022-09-30 22:25 Palmer Dabbelt
0 siblings, 0 replies; only message in thread
From: Palmer Dabbelt @ 2022-09-30 22:25 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:4dcd340ebaae8213eeae89894b5ecdf61b0eb100
commit r13-3001-g4dcd340ebaae8213eeae89894b5ecdf61b0eb100
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date: Fri Sep 9 02:46:40 2022 -0700
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.
Diff:
---
gcc/doc/tm.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index 858bfb80cec..7590924f2ca 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},
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-09-30 22:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-30 22:25 [gcc r13-3001] Document -fexcess-precision=16 in tm.texi Palmer Dabbelt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).