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/105480] Vectorized `isnan` appears to trigger FPE on ppc64le Date: Wed, 02 Nov 2022 20:10:40 +0000 [thread overview] Message-ID: <bug-105480-4-nxnjbBvw7L@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|powerpc64le-linux |powerpc64*-linux-* --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- During expand: (insn 20 19 21 (set (reg:V2DF 149) (unordered:V2DF (reg:V2DF 128 [ vect__7.7 ]) (reg:V2DF 128 [ vect__7.7 ]))) -1 (nil)) Which is correct. after combine: (insn 26 21 27 3 (set (reg:V2DF 154) (unordered:V2DF (reg:V2DF 144 [ vect__7.8 ]) (reg:V2DF 144 [ vect__7.8 ]))) 1138 {vector_unorderedv2df} (expr_list:REG_DEAD (reg:V2DF 144 [ vect__7.8 ]) (nil))) So basically the splitter here goes wrong: ; For ltgt/uneq/ordered/unordered: ; ltgt: gt(a,b) | gt(b,a) ; uneq: ~(gt(a,b) | gt(b,a)) ; ordered: ge(a,b) | ge(b,a) ; unordered: ~(ge(a,b) | ge(b,a)) (define_insn_and_split Someone else needs to look into making sure these are valid for trapping math case ...
next prev parent reply other threads:[~2022-11-02 20:10 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 2022-11-02 20:00 ` pinskia at gcc dot gnu.org 2022-11-02 20:10 ` pinskia at gcc dot gnu.org [this message] 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-nxnjbBvw7L@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: linkBe 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).