public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/112343] New: [14 regression] ICE during GIMPLE pass: dse Date: Wed, 01 Nov 2023 21:33:11 +0000 [thread overview] Message-ID: <bug-112343-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112343 Bug ID: 112343 Summary: [14 regression] ICE during GIMPLE pass: dse Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: gerald at pfeifer dot com Target Milestone: --- Created attachment 56486 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56486&action=edit Preprocessed C source This started in the last 48 hours. /home/gerald/gcc-ref12-amd64/bin/gcc> jcparam.i -O2 -g during GIMPLE pass: dse jcparam.c: In function ‘jpeg_simple_progression’: jcparam.c:514:1: internal compiler error: Segmentation fault 514 | jpeg_simple_progression (j_compress_ptr cinfo) | ^~~~~~~~~~~~~~~~~~~~~~~ 0x829785baf handle_signal /usr/src/lib/libthr/thread/thr_sig.c:248 0x82978516e thr_sighandler /usr/src/lib/libthr/thread/thr_sig.c:191 If I use -O1 instead of -O2 or omit -g the ICE goes away.
next reply other threads:[~2023-11-01 21:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 21:33 gerald at pfeifer dot com [this message] 2023-11-01 22:45 ` [Bug debug/112343] " pinskia 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-112343-4@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).