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/94856] [10 Regression] ICE: Segmentation fault (in clone_of_p); or ICE: verify_cgraph_node failed (error: edge points to wrong declaration) since r10-4944-g1e83bd7003e03160 Date: Thu, 30 Apr 2020 08:01:20 +0000 [thread overview] Message-ID: <bug-94856-4-UdZ6g4ERNm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94856-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94856 --- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- Reduced test-case: class a { public: virtual ~a() {} }; class b { public: virtual void c(); }; class C : a, public b {}; class d : C { ~d(); void c(); }; d::~d() { ((b *)this)->c(); } void d::c() {}
next prev parent reply other threads:[~2020-04-30 8:01 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 17:43 [Bug ipa/94856] New: [10 Regression] ICE: Segmentation fault (in clone_of_p); or ICE: verify_cgraph_node failed (error: edge points to wrong declaration) asolokha at gmx dot com 2020-04-29 19:10 ` [Bug ipa/94856] [10 Regression] ICE: Segmentation fault (in clone_of_p); or ICE: verify_cgraph_node failed (error: edge points to wrong declaration) since r10-4944-g1e83bd7003e03160 marxin at gcc dot gnu.org 2020-04-29 19:12 ` marxin at gcc dot gnu.org 2020-04-30 6:45 ` rguenth at gcc dot gnu.org 2020-04-30 8:01 ` marxin at gcc dot gnu.org [this message] 2020-04-30 8:49 ` marxin at gcc dot gnu.org 2020-04-30 8:51 ` marxin at gcc dot gnu.org 2020-04-30 10:30 ` jamborm at gcc dot gnu.org 2020-04-30 14:37 ` jamborm at gcc dot gnu.org 2020-04-30 15:59 ` [Bug ipa/94856] [10/11 " cvs-commit at gcc dot gnu.org 2020-04-30 16:08 ` cvs-commit at gcc dot gnu.org 2020-04-30 16:23 ` jamborm 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-94856-4-UdZ6g4ERNm@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).