public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106815] [13 Regression] ICE: in riscv_excess_precision, at config/riscv/riscv.cc:5967 with -fexcess-precision=16 on any input
Date: Fri, 30 Sep 2022 22:23:25 +0000	[thread overview]
Message-ID: <bug-106815-4-lI1uGQKigJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106815-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106815

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Palmer Dabbelt <palmer@gcc.gnu.org>:

https://gcc.gnu.org/g:75c0899493cd84e64bd30210e848d0d1e9979494

commit r13-3000-g75c0899493cd84e64bd30210e848d0d1e9979494
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Fri Sep 9 02:43:26 2022 -0700

    RISC-V: Support -fexcess-precision=16

    This fixes f19a327077e ("Support -fexcess-precision=16 which will enable
    FLT_EVAL_METHOD_PROMOTE_TO_FLOAT16 when backend supports _Float16.") on
    RISC-V targets.

    gcc/ChangeLog

            PR target/106815
            * config/riscv/riscv.cc (riscv_excess_precision): Add support
            for EXCESS_PRECISION_TYPE_FLOAT16.

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 14:08 [Bug target/106815] New: " zsojka at seznam dot cz
2022-09-03  1:31 ` [Bug target/106815] " palmer at gcc dot gnu.org
2022-09-05 10:00 ` rguenth at gcc dot gnu.org
2022-09-30 22:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-19  6:11 ` rguenth at gcc dot gnu.org

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=bug-106815-4-lI1uGQKigJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).