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 middle-end/104558] [9/10/11 Regression] ICE: in expand_call, at calls.cc:3601 with -fabi-version=9 on pr83487.c Date: Thu, 03 Mar 2022 08:34:14 +0000 [thread overview] Message-ID: <bug-104558-4-ZQyPdQHMUd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104558 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[9/10/11/12 Regression] |[9/10/11 Regression] ICE: |ICE: in expand_call, at |in expand_call, at |calls.cc:3601 with |calls.cc:3601 with |-fabi-version=9 on |-fabi-version=9 on |pr83487.c |pr83487.c --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Fixed on the trunk. I think for backports we'd need a proof that we always ICE or at least that if it doesn't ICE the callers are ABI incompatible with callees.
next prev parent reply other threads:[~2022-03-03 8:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 20:21 [Bug tree-optimization/104558] New: [9/10/11/12 " zsojka at seznam dot cz 2022-02-16 11:18 ` [Bug tree-optimization/104558] " jakub at gcc dot gnu.org 2022-02-16 11:53 ` jakub at gcc dot gnu.org 2022-02-16 12:28 ` [Bug middle-end/104558] " jakub at gcc dot gnu.org 2022-03-03 8:12 ` cvs-commit at gcc dot gnu.org 2022-03-03 8:34 ` jakub at gcc dot gnu.org [this message] 2022-05-27 9:47 ` [Bug middle-end/104558] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug middle-end/104558] [11 " rguenth 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-104558-4-ZQyPdQHMUd@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).