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/95169] [10/11 Regression] i386 comparison between nan and 0.0 triggers Invalid operation exception
Date: Thu, 21 May 2020 17:37:21 +0000	[thread overview]
Message-ID: <bug-95169-4-W2K6mJUL26@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95169-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Uros Bizjak <uros@gcc.gnu.org>:

https://gcc.gnu.org/g:ddfb80adbd91a0e45cc6e04a8b0dbe3ca15ba45f

commit r10-8167-gddfb80adbd91a0e45cc6e04a8b0dbe3ca15ba45f
Author: Uros Bizjak <ubizjak@gmail.com>
Date:   Thu May 21 19:36:32 2020 +0200

    i386: Avoid reversing a non-trapping comparison to a trapping one [PR95169]

    2020-05-21  Uroš Bizjak  <ubizjak@gmail.com>

    gcc/ChangeLog:
            PR target/95169
            * config/i386/i386-expand.c (ix86_expand_int_movcc):
             Avoid reversing a non-trapping comparison to a trapping one.

    gcc/testsuite/ChangeLog:
            PR target/95169
            * gcc.target/i386/pr95169.c: New test.

  parent reply	other threads:[~2020-05-21 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17  0:23 [Bug c/95169] New: " samuel.thibault@ens-lyon.org
2020-05-17  0:25 ` [Bug c/95169] " samuel.thibault@ens-lyon.org
2020-05-17  0:26 ` samuel.thibault@ens-lyon.org
2020-05-17  1:06 ` [Bug target/95169] " samuel.thibault@ens-lyon.org
2020-05-17  1:59 ` pinskia at gcc dot gnu.org
2020-05-17 18:32 ` ubizjak at gmail dot com
2020-05-17 18:58 ` ubizjak at gmail dot com
2020-05-18 15:53 ` [Bug target/95169] [10/11 Regression] " cvs-commit at gcc dot gnu.org
2020-05-21 17:37 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-21 18:43 ` ubizjak at gmail dot com

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-95169-4-W2K6mJUL26@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).