public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102607] New: [modules] option -g results in undefined reference to `typeinfo for type` Date: Tue, 05 Oct 2021 14:43:51 +0000 [thread overview] Message-ID: <bug-102607-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102607 Bug ID: 102607 Summary: [modules] option -g results in undefined reference to `typeinfo for type` Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: link-failure Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: johelegp at gmail dot com CC: johelegp at gmail dot com Target Milestone: --- See https://godbolt.org/z/qP6EPWhEz. mod.cpp: ```C++ export module mod; export struct B { virtual ~B() = default; }; ``` main.cpp: ```C++ import mod; int main() { struct D : B {}; (void)D{}; } ``` Commands: ``` g++ -std=c++23 -fmodules-ts -g -c mod.cpp g++ -std=c++23 -fmodules-ts -g -c main.cpp g++ mod.o main.o ``` Output: ``` /usr/bin/ld: main.o:(.data.rel.ro+0x8): undefined reference to `typeinfo for B' /usr/bin/ld: main.o:(.data.rel.ro+0x30): undefined reference to `typeinfo for B' collect2: error: ld returned 1 exit status ```
next reply other threads:[~2021-10-05 14:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 14:43 johelegp at gmail dot com [this message] 2021-10-05 19:23 ` [Bug c++/102607] " johelegp at gmail dot com 2024-01-23 9:46 ` cvs-commit at gcc dot gnu.org 2024-01-27 10:26 ` nshead 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-102607-4@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).