public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3001] Document -fexcess-precision=16 in tm.texi
Date: Fri, 30 Sep 2022 22:25:23 +0000 (GMT)	[thread overview]
Message-ID: <20220930222523.649353858D38@sourceware.org> (raw)

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},

                 reply	other threads:[~2022-09-30 22:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220930222523.649353858D38@sourceware.org \
    --to=palmer@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).