public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/112815] ICE: in vague_linkage_p, at cp/decl2.cc:2329 with -flto -fno-weak Date: Thu, 18 Jan 2024 19:44:25 +0000 [thread overview] Message-ID: <bug-112815-4-xCX49axmaW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112815-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112815 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Component|c++ |ipa Last reconfirmed| |2024-01-18 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Confirmed. Started with r6-1066-g233ce289250944: commit 233ce289250944dde071638799f9ba1a51a0a9bf Author: Jan Hubicka <hubicka@ucw.cz> Date: Sun May 24 21:38:14 2015 +0200 re PR lto/66180 (many -Wodr false positives when building LLVM with -flto) PR lto/66180 * ipa-devirt.c (type_with_linkage): Check that TYPE_STUB_DECL is set; check for assembler name at LTO time. (type_in_anonymous_namespace): Remove hacks, check that all anonymous types are called "<anon>" (odr_type_p): Simplify; add check for "<anon>" (odr_subtypes_equivalent): Add odr_type_p check. * tree.c (need_assembler_name_p): Even anonymous namespace needs assembler name. * mangle.c (mangle_decl): Mangle anonymous namespace types as "<anon>". * g++.dg/lto/pr66180_0.C: New testcase. * g++.dg/lto/pr66180_1.C: New testcase. From-SVN: r223633
next prev parent reply other threads:[~2024-01-18 19:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-01 21:07 [Bug c++/112815] New: " zsojka at seznam dot cz 2024-01-18 19:44 ` mpolacek at gcc dot gnu.org [this message] 2024-01-18 19:44 ` [Bug ipa/112815] [11/12/13/14 Regression] " mpolacek at gcc dot gnu.org 2024-03-07 21:00 ` law at gcc dot gnu.org 2024-03-12 13:22 ` jakub 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-112815-4-xCX49axmaW@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).