public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Document -fexcess-precision=16 in tm.texi
Date: Sun, 18 Sep 2022 01:47:37 -0700 (PDT)	[thread overview]
Message-ID: <mhng-093aa182-ef6b-48d4-9b05-62aec456ec6d@palmer-ri-x1c9> (raw)
In-Reply-To: <20220909094640.24077-1-palmer@rivosinc.com>

On Fri, 09 Sep 2022 02:46:40 PDT (-0700), Palmer Dabbelt wrote:
> 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.
> ---
>  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},

Just pinging this one as I'm not sure if it's OK to self-approve -- no 
rush on my end, I already figured it out so I don't need the 
documentation any more.

  reply	other threads:[~2022-09-18  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  9:46 Palmer Dabbelt
2022-09-18  8:47 ` Palmer Dabbelt [this message]
2022-09-25  2:13   ` Sandra Loosemore
2022-09-30 22:25     ` Palmer Dabbelt
2022-09-30 22:51       ` H.J. Lu
2022-09-30 22:58         ` Palmer Dabbelt

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=mhng-093aa182-ef6b-48d4-9b05-62aec456ec6d@palmer-ri-x1c9 \
    --to=palmer@dabbelt.com \
    --cc=gcc-patches@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).