public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106122] New: [12/13 Regression] ICE in fixup_args_size_notes, at expr.cc:4493 Date: Tue, 28 Jun 2022 17:06:55 +0000 [thread overview] Message-ID: <bug-106122-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106122 Bug ID: 106122 Summary: [12/13 Regression] ICE in fixup_args_size_notes, at expr.cc:4493 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20211219 and 20220109, with -Oz and file gcc.target/i386/pr104446.c : $ gcc-12-20211219 -c pr104446.c -m32 -Oz $ $ gcc-13-20220626 -c pr104446.c -m32 -Oz during RTL pass: peephole2 pr104446.c: In function 'baz': pr104446.c:15:1: internal compiler error: in fixup_args_size_notes, at expr.cc:4493 15 | } | ^ 0x8d72ec fixup_args_size_notes(rtx_insn*, rtx_insn*, poly_int<1u, long>) ../../gcc/expr.cc:4493 0xb98f36 peep2_attempt ../../gcc/recog.cc:4014 0xb98f36 peephole2_optimize ../../gcc/recog.cc:4183 0xb98f36 rest_of_handle_peephole2 ../../gcc/recog.cc:4331 0xb98f36 execute ../../gcc/recog.cc:4365
next reply other threads:[~2022-06-28 17:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-28 17:06 gscfq@t-online.de [this message] 2022-06-29 9:44 ` [Bug target/106122] " rguenth at gcc dot gnu.org 2022-06-29 12:05 ` [Bug target/106122] [12/13 Regression] ICE in fixup_args_size_notes, at expr.cc:4493 since r12-6106-gef26c151c14a8717 marxin at gcc dot gnu.org 2022-06-29 13:03 ` roger at nextmovesoftware dot com 2022-07-01 8:20 ` cvs-commit at gcc dot gnu.org 2022-07-03 13:02 ` cvs-commit at gcc dot gnu.org 2022-07-03 13:23 ` roger at nextmovesoftware 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-106122-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).