public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/110220] [13/14 Regression] ICE in patch_jump_insn, at cfgrtl.cc:1295 - avr/xmega Date: Fri, 30 Jun 2023 16:29:53 +0000 [thread overview] Message-ID: <bug-110220-4-xFbhDCIv1r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110220-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110220 Georg-Johann Lay <gjl at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gjl at gcc dot gnu.org --- Comment #6 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- I can reproduce Andi's testcase, and with -fdisable-rtl-avr-casesi the ICE goes away. Hence 1) This is just an accident, or 2) There is a bug in avr-specific pass avr-casesi (as dumped with -fdump-rtl-avr-casesi) like wrong RTL-sharing or such, or 3) cfgrtl's assertion is too strict and effectively disallows such target-specific (optimization) passes. I don't currently have time to look into this in a timely manner.
next prev parent reply other threads:[~2023-06-30 16:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-12 11:33 [Bug rtl-optimization/110220] New: " daniel at rozsnyo dot com 2023-06-12 16:13 ` [Bug rtl-optimization/110220] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-12 16:22 ` pinskia at gcc dot gnu.org 2023-06-12 16:25 ` daniel at rozsnyo dot com 2023-06-12 16:28 ` pinskia at gcc dot gnu.org 2023-06-12 16:28 ` pinskia at gcc dot gnu.org 2023-06-30 16:29 ` gjl at gcc dot gnu.org [this message] 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-08-01 11:51 ` cvs-commit at gcc dot gnu.org 2023-08-01 13:02 ` cvs-commit at gcc dot gnu.org 2023-08-01 13:05 ` [Bug target/110220] " gjl 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-110220-4-xFbhDCIv1r@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).