| Message ID | 20220909094640.24077-1-palmer@rivosinc.com |
|---|---|
| State | Committed |
| Commit | 4dcd340ebaae8213eeae89894b5ecdf61b0eb100 |
| Headers |
Return-Path: <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 04C703857356 for <patchwork@sourceware.org>; Fri, 9 Sep 2022 09:47:24 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) by sourceware.org (Postfix) with ESMTPS id DCF3538582BF for <gcc-patches@gcc.gnu.org>; Fri, 9 Sep 2022 09:47:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DCF3538582BF Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=rivosinc.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=rivosinc.com Received: by mail-pg1-x52e.google.com with SMTP id bh13so1072747pgb.4 for <gcc-patches@gcc.gnu.org>; Fri, 09 Sep 2022 02:47:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rivosinc-com.20210112.gappssmtp.com; s=20210112; h=to:from:cc:content-transfer-encoding:mime-version:message-id:date :subject:from:to:cc:subject:date; bh=LlRb59sX9eKzr10B41uPGe/A98XeuaRdT6wEbxi/p14=; b=3WQpuZPTRK/ns9Q6SURqw2H0mX9x5A6tWoFXEXwksU3htDcVF59FCHGH5/hCx/C8SX TSzcE3d9KY8mNNmhcGabxgEH//whn72uzASOeU+HsgYdwhWznjYnOQ1stIOFoYpDUMpG BIv6HoXKCSpKHP2je1lgi8pLYP8NM5lNy0nMd5m2bs/yqqXQVYyi9tIuuccMVzwvY+P7 m2Z/Et/LXT3k6KonVB2kpklJGOT9Fge5RyQB4dNOJ3E7ljheUXqTGFPCbfN0eOGNpw2Z D3wzWKm0gnlsAZimS1lOe/4HN7MT4fuWx7ctFYf3HRin/IZdIb4dKGXwN0T8MclKf2vu w5OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:cc:content-transfer-encoding:mime-version:message-id:date :subject:x-gm-message-state:from:to:cc:subject:date; bh=LlRb59sX9eKzr10B41uPGe/A98XeuaRdT6wEbxi/p14=; b=k816ut4fRG6qJ73b91RK6xjzWV+1ArNXJJH3JDKEAAfli15lIRiLfAa6cs4zCOMzms WzOkySFdosM/c38sY6yooM4nOFxvr7XttF42oW5LtmNj1MhcMdF21x1LnNvtw0cUnqlX W1yvwOy5BXJET5/YIIQYpTW34T+L9m0G82ZJkO89vvxJw+wOF7/XKzSGlUmJE/2o6XDz pKtH0tg4akfQK/B54xK0DkYk8A5Y8OTfT15eXeUn9PK7DyLvZVxahtRnxSuaLI/9Be1/ lUG5usH6LBDPYv4K7IsYc5uVx+TO/pffu5HlPhmQ7tHzDewA8GsjGw0M46DTAtWgIIXv vJVw== X-Gm-Message-State: ACgBeo0eY1VOkUhNRGyapbVnR3qaGiYyg70+qoQoGDiv+9iHE0a7kgTD pfECcrQBFw6QlX8nId4s4OoLHg== X-Google-Smtp-Source: AA6agR7ZheLwI1VsNte7W/eRmLlX/T2L/aA76IC/8wJ/PEh9z07+AuO06uastCz8zhnAhDf2Eyh3gg== X-Received: by 2002:a63:564b:0:b0:42c:414a:95fd with SMTP id g11-20020a63564b000000b0042c414a95fdmr11454628pgm.5.1662716825931; Fri, 09 Sep 2022 02:47:05 -0700 (PDT) Received: from localhost ([51.52.155.79]) by smtp.gmail.com with ESMTPSA id w3-20020a626203000000b00540f3ac5fb8sm103008pfb.69.2022.09.09.02.47.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Sep 2022 02:47:05 -0700 (PDT) Subject: [PATCH] Document -fexcess-precision=16 in tm.texi Date: Fri, 9 Sep 2022 02:46:40 -0700 Message-Id: <20220909094640.24077-1-palmer@rivosinc.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Palmer Dabbelt <palmer@rivosinc.com> To: gcc-patches@gcc.gnu.org X-Spam-Status: No, score=-12.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, GIT_PATCH_0, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org> List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe> List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/> List-Post: <mailto:gcc-patches@gcc.gnu.org> List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help> List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe> Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org Sender: "Gcc-patches" <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> |
| Series |
Document -fexcess-precision=16 in tm.texi
|
|
Commit Message
Palmer Dabbelt
Sept. 9, 2022, 9:46 a.m. UTC
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(-)
Comments
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.
On 9/18/22 02:47, Palmer Dabbelt wrote: > 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. This is fine, looks like a trivial correction. -Sandra
On Sat, 24 Sep 2022 19:13:36 PDT (-0700), sandra@codesourcery.com wrote: > On 9/18/22 02:47, Palmer Dabbelt wrote: >> 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. > > This is fine, looks like a trivial correction. Thanks, committed.
On Fri, Sep 30, 2022 at 3:25 PM Palmer Dabbelt <palmer@dabbelt.com> wrote: > > On Sat, 24 Sep 2022 19:13:36 PDT (-0700), sandra@codesourcery.com wrote: > > On 9/18/22 02:47, Palmer Dabbelt wrote: > >> 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. > > > > This is fine, looks like a trivial correction. > > Thanks, committed. tm.texi is a generated file. I am checking in this patch to restore bootstrap.
On Fri, 30 Sep 2022 15:51:02 PDT (-0700), H.J. Lu wrote: > On Fri, Sep 30, 2022 at 3:25 PM Palmer Dabbelt <palmer@dabbelt.com> wrote: >> >> On Sat, 24 Sep 2022 19:13:36 PDT (-0700), sandra@codesourcery.com wrote: >> > On 9/18/22 02:47, Palmer Dabbelt wrote: >> >> 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. >> > >> > This is fine, looks like a trivial correction. >> >> Thanks, committed. > > tm.texi is a generated file. I am checking in this patch to restore bootstrap. Sorry about that, and thanks for fixing it.
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},