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 middle-end/95115] RISC-V 64: inf/inf division optimized out, invalid operation not raised
Date: Tue, 01 Feb 2022 10:21:46 +0000	[thread overview]
Message-ID: <bug-95115-4-ONMFnNSmZ9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95115-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:

https://gcc.gnu.org/g:34afa19d29c5bf0b0f504e4d0aca4e9a8bc82c5c

commit r12-6959-g34afa19d29c5bf0b0f504e4d0aca4e9a8bc82c5c
Author: Xi Ruoyao <xry111@mengyan1223.wang>
Date:   Mon Jan 31 01:15:20 2022 +0800

    fold-const: do not fold NaN result from non-NaN operands [PR95115]

    These operations should raise an invalid operation exception at runtime.
    So they should not be folded during compilation unless -fno-trapping-math
    is used.

    gcc/
            PR middle-end/95115
            * fold-const.cc (const_binop): Do not fold NaN result from
              non-NaN operands.

    gcc/testsuite
            * gcc.dg/pr95115.c: New test.

  parent reply	other threads:[~2022-02-01 10:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 20:08 [Bug target/95115] New: [10 Regression] " aurelien at aurel32 dot net
2020-05-13 20:45 ` [Bug target/95115] " glisse at gcc dot gnu.org
2020-05-13 20:58 ` glisse at gcc dot gnu.org
2020-05-14  3:51 ` wilson at gcc dot gnu.org
2020-05-14  5:33 ` glisse at gcc dot gnu.org
2020-05-14  6:05 ` aurelien at aurel32 dot net
2020-05-14  6:33 ` [Bug middle-end/95115] " rguenth at gcc dot gnu.org
2020-07-02 19:52 ` vgupta at synopsys dot com
2022-01-30 16:44 ` xry111 at mengyan1223 dot wang
2022-02-01 10:21 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-02  5:19 ` cvs-commit at gcc dot gnu.org
2022-02-02  9:25 ` cvs-commit at gcc dot gnu.org
2022-02-02 14:06 ` xry111 at mengyan1223 dot wang
2022-02-02 22:32 ` pinskia 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-95115-4-ONMFnNSmZ9@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).