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 bootstrap/98414] [11 Regression] UBSAN bootstrap is broken: ubsan/ubsan_type_hash_itanium.cpp:162: undefined reference to `__dynamic_cast' since r11-6083-gb7dfc2074c78415d451eb34d1608016c80b1c41a Date: Tue, 05 Jan 2021 14:08:22 +0000 [thread overview] Message-ID: <bug-98414-4-DUsJ2KhBjc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98414 --- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> --- I replaced cp/mapper-client.o cp/mapper-resolver.o just with: $ cat mapper-resolver.ii namespace Cody { enum class Flags : unsigned; class Resolver { virtual int IncludeTranslateRequest(int *s, Flags flags, int &include); }; } // namespace Cody class module_resolver : public Cody::Resolver { virtual int IncludeTranslateRequest(int *s, Cody::Flags, int &include) override; private: }; int module_resolver::IncludeTranslateRequest(int *s, Cody::Flags, int &include) {} which needs the symbol: nm mapper-resolver.o ... U _ZTVN10__cxxabiv120__si_class_type_infoE Jakub: Does it confirm your description. Do you know how to fix that?
next prev parent reply other threads:[~2021-01-05 14:08 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-21 15:22 [Bug bootstrap/98414] New: [11 Regression] UBSAN bootstrap is broken: ubsan/ubsan_type_hash_itanium.cpp:162: undefined reference to `__dynamic_cast' marxin at gcc dot gnu.org 2020-12-21 15:23 ` [Bug bootstrap/98414] " marxin at gcc dot gnu.org 2021-01-05 9:37 ` rguenth at gcc dot gnu.org 2021-01-05 10:37 ` marxin at gcc dot gnu.org 2021-01-05 12:40 ` [Bug bootstrap/98414] [11 Regression] UBSAN bootstrap is broken: ubsan/ubsan_type_hash_itanium.cpp:162: undefined reference to `__dynamic_cast' since r11-6083-gb7dfc2074c78415d451eb34d1608016c80b1c41a marxin at gcc dot gnu.org 2021-01-05 13:44 ` nathan at gcc dot gnu.org 2021-01-05 13:51 ` jakub at gcc dot gnu.org 2021-01-05 14:08 ` marxin at gcc dot gnu.org [this message] 2021-01-05 14:10 ` marxin at gcc dot gnu.org 2021-01-05 14:14 ` jakub at gcc dot gnu.org 2021-01-05 14:24 ` marxin at gcc dot gnu.org 2021-01-07 13:32 ` marxin at gcc dot gnu.org 2021-01-11 9:54 ` marxin at gcc dot gnu.org 2021-01-11 9:59 ` marxin at gcc dot gnu.org 2021-01-11 10:02 ` jakub at gcc dot gnu.org 2021-01-11 10:06 ` marxin at gcc dot gnu.org 2021-01-11 10:22 ` marxin at gcc dot gnu.org 2021-01-11 10:48 ` marxin at gcc dot gnu.org 2021-01-11 12:55 ` nathan at gcc dot gnu.org 2021-01-12 18:33 ` nathan 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-98414-4-DUsJ2KhBjc@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).