public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/104533] [12 Regression] ICE in update_vtable_references, at ipa-visibility.cc:383 since r12-2900-gfa28520fadb9405f Date: Tue, 22 Feb 2022 10:12:07 +0000 [thread overview] Message-ID: <bug-104533-4-AxVO6Fibtg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104533-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104533 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[12 Regression] ICE in |[12 Regression] ICE in |update_vtable_references, |update_vtable_references, |at ipa-visibility.cc:383 |at ipa-visibility.cc:383 | |since | |r12-2900-gfa28520fadb9405f Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- With: g++ pr104533.C -c -fPIC -Ofast -fno-semantic-interposition it crashes since r12-2900-gfa28520fadb9405f. I can take a look.
next prev parent reply other threads:[~2022-02-22 10:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-14 19:55 [Bug c++/104533] New: [12 Regression] ICE in update_vtable_references, at ipa-visibility.cc:383 gscfq@t-online.de 2022-02-15 8:03 ` [Bug ipa/104533] " rguenth at gcc dot gnu.org 2022-02-16 10:06 ` pinskia at gcc dot gnu.org 2022-02-22 10:12 ` marxin at gcc dot gnu.org [this message] 2022-03-01 9:10 ` [Bug ipa/104533] [12 Regression] ICE in update_vtable_references, at ipa-visibility.cc:383 since r12-2900-gfa28520fadb9405f cvs-commit at gcc dot gnu.org 2022-03-01 9:11 ` marxin 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-104533-4-AxVO6Fibtg@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).