public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112962] [14 Regression] ICE: SIGSEGV in operator()<rtx_def*, rtx_def*> (recog.h:431) with -fexceptions -mssse3 and __builtin_ia32_pabsd128() Date: Tue, 12 Dec 2023 09:39:47 +0000 [thread overview] Message-ID: <bug-112962-4-BROzFvA26v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112962-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112962 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- With -O1 or higher there is some DCE which will remove them (unless disabled), but the above ICE is with -O0...
next prev parent reply other threads:[~2023-12-12 9:39 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-11 14:59 [Bug target/112962] New: " zsojka at seznam dot cz 2023-12-12 7:21 ` [Bug target/112962] " rguenth at gcc dot gnu.org 2023-12-12 9:05 ` ubizjak at gmail dot com 2023-12-12 9:36 ` jakub at gcc dot gnu.org 2023-12-12 9:38 ` jakub at gcc dot gnu.org 2023-12-12 9:38 ` ubizjak at gmail dot com 2023-12-12 9:39 ` jakub at gcc dot gnu.org [this message] 2023-12-12 9:54 ` ubizjak at gmail dot com 2023-12-12 10:03 ` jakub at gcc dot gnu.org 2023-12-12 10:08 ` jakub at gcc dot gnu.org 2023-12-12 10:12 ` ubizjak at gmail dot com 2023-12-12 10:15 ` ubizjak at gmail dot com 2023-12-12 10:36 ` jakub at gcc dot gnu.org 2023-12-12 11:06 ` liuhongt at gcc dot gnu.org 2023-12-12 11:08 ` liuhongt at gcc dot gnu.org 2023-12-12 11:24 ` jakub at gcc dot gnu.org 2023-12-12 11:26 ` jakub at gcc dot gnu.org 2023-12-12 22:59 ` pinskia at gcc dot gnu.org 2023-12-13 10:34 ` cvs-commit at gcc dot gnu.org 2023-12-13 11:10 ` jakub at gcc dot gnu.org 2023-12-20 11:02 ` cvs-commit at gcc dot gnu.org
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-112962-4-BROzFvA26v@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).