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/102080] [12 Regression] avx512vl related ICE, on firefox-92 gcc ICEs: in expand_insn, at optabs.c:7946 by r12-2679 Date: Fri, 27 Aug 2021 02:23:54 +0000 [thread overview] Message-ID: <bug-102080-4-GohlCaOf37@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102080-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This is the match pattern which does it: (for uncond_op (UNCOND_BINARY) cond_op (COND_BINARY) (simplify (vec_cond @0 (view_convert? (uncond_op@4 @1 @2)) @3) (with { tree op_type = TREE_TYPE (@4); } (if (vectorized_internal_fn_supported_p (as_internal_fn (cond_op), op_type) && element_precision (type) == element_precision (op_type)) (view_convert (cond_op @0 @1 @2 (view_convert:op_type @3)))))) (simplify (vec_cond @0 @1 (view_convert? (uncond_op@4 @2 @3))) (with { tree op_type = TREE_TYPE (@4); } (if (vectorized_internal_fn_supported_p (as_internal_fn (cond_op), op_type) && element_precision (type) == element_precision (op_type)) (view_convert (cond_op (bit_not @0) @2 @3 (view_convert:op_type @1))))))) I don't see anything wrong here. Are we saying the (bit_not @0) part is causing issues?
next prev parent reply other threads:[~2021-08-27 2:23 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-26 14:42 [Bug target/102080] New: [12 Regression] avx512vl related ICE, on firefox-92 gcc ICEs: in expand_insn, at optabs.c:7946 slyfox at gcc dot gnu.org 2021-08-26 14:46 ` [Bug target/102080] " slyfox at gcc dot gnu.org 2021-08-26 16:10 ` [Bug target/102080] [12 Regression] avx512vl related ICE, on firefox-92 gcc ICEs: in expand_insn, at optabs.c:7946 by r12-2679 hjl.tools at gmail dot com 2021-08-27 0:38 ` crazylht at gmail dot com 2021-08-27 2:16 ` crazylht at gmail dot com 2021-08-27 2:19 ` pinskia at gcc dot gnu.org 2021-08-27 2:23 ` pinskia at gcc dot gnu.org [this message] 2021-08-27 2:32 ` pinskia at gcc dot gnu.org 2021-08-27 2:33 ` pinskia at gcc dot gnu.org 2021-08-27 2:42 ` crazylht at gmail dot com 2021-08-27 2:52 ` [Bug middle-end/102080] " pinskia at gcc dot gnu.org 2021-08-27 5:17 ` crazylht at gmail dot com 2021-08-27 7:02 ` rguenth at gcc dot gnu.org 2021-08-27 8:29 ` marxin at gcc dot gnu.org 2021-08-27 8:30 ` marxin at gcc dot gnu.org 2021-09-16 8:35 ` cvs-commit at gcc dot gnu.org 2021-12-17 16:01 ` jakub at gcc dot gnu.org 2021-12-17 16:07 ` hjl.tools 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-102080-4-GohlCaOf37@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).