public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian-gcc at sipsolutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105480] Vectorized `isnan` appears to trigger FPE on ppc64le
Date: Thu, 05 May 2022 08:14:18 +0000	[thread overview]
Message-ID: <bug-105480-4-C6ZausNaFz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105480-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from seberg <sebastian-gcc at sipsolutions dot net> ---
I still owed the correct example: https://godbolt.org/z/33Pj6xvPr

Now I think the cause is the indeed (somewhat understandandable) desire to
optimize away the branching.  And not the instruction (I am not sure how the
comparison instruction deals with trapping, so it could be both).

  parent reply	other threads:[~2022-05-05  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 13:15 [Bug target/105480] New: " sebastian-gcc at sipsolutions dot net
2022-05-04 14:21 ` [Bug target/105480] " sebastian-gcc at sipsolutions dot net
2022-05-05  8:14 ` sebastian-gcc at sipsolutions dot net [this message]
2022-11-02 20:00 ` pinskia at gcc dot gnu.org
2022-11-02 20:10 ` pinskia at gcc dot gnu.org
2022-11-08  7:14 ` linkw at gcc dot gnu.org
2022-11-09  8:31 ` linkw at gcc dot gnu.org
2022-11-09  8:48 ` rguenth at gcc dot gnu.org
2022-11-09  8:59 ` linkw at gcc dot gnu.org
2022-11-09 13:08 ` rguenth at gcc dot gnu.org
2022-11-09 17:30 ` joseph at codesourcery dot com
2022-11-10  5:58 ` linkw at gcc dot gnu.org
2022-11-10 23:42 ` joseph at codesourcery 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-105480-4-C6ZausNaFz@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).