public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95169] i386 comparison between nan and 0.0 triggers Invalid operation exception
Date: Sun, 17 May 2020 01:59:12 +0000	[thread overview]
Message-ID: <bug-95169-4-iFfwAJVjDo@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 #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
   0x000011e6 <+45>:    fcompl -0x10(%ebp)
   0x000011e9 <+48>:    fnstsw %ax
   0x000011eb <+50>:    sahf   

That is what raises the invalid-operation exception

#(insn 23 56 24 2 (set (reg:HI 0 ax [99])
#        (unspec:HI [
#                (compare:CCFP (reg:DF 8 st)
#                    (mem/c:DF (plus:SI (reg/f:SI 6 bp)
#                            (const_int -16 [0xfffffffffffffff0])) [1 y+0 S8
A64]))
#            ] UNSPEC_FNSTSW)) "t6.c":6:25 23 {*cmpdf_i387}
#     (expr_list:REG_DEAD (reg:DF 8 st)
#        (nil)))
        fcompl  -16(%ebp)       # 23    [c=20 l=16]  *cmpdf_i387

  parent reply	other threads:[~2020-05-17  1:59 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 [this message]
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
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-iFfwAJVjDo@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).