public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99377] [modules] undefined std::string_view::empty() if referenced in inline exported function Date: Wed, 12 Oct 2022 15:13:31 +0000 [thread overview] Message-ID: <bug-99377-4-PnahWZNOpo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99377-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99377 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ppalka at gcc dot gnu.org --- Comment #15 from Patrick Palka <ppalka at gcc dot gnu.org> --- The comment #5 testcase now works on trunk, but the comment #4 testcase still fails to link. Reduced: $ cat 99377_a.H template<typename> struct Widget { Widget (int) { } bool First() const { return true; } bool Second () const { return true;} }; inline void Frob (const Widget<int>& w) noexcept { w.First (); } $ 99377_b.C export module Foo:check; import "99377_a.H"; export inline bool Check (const Widget<int>& w) { return w.Second (); } $ cat 99377_c.C export module Foo; export import :check; $ cat 99377_d.C import Foo; int main () { return Check (0) ? 0 : 1; } $ g++ -fmodules-ts 99377_a.H 99377_b.C 99377_c.C 99377_d.C /usr/bin/ld: /tmp/ccBHt33S.o: in function `Check@Foo(Widget<int> const&)': 99377_d.C:(.text._ZW3Foo5CheckRK6WidgetIiE[_ZW3Foo5CheckRK6WidgetIiE]+0x14): undefined reference to `Widget<int>::Second() const'
next prev parent reply other threads:[~2022-10-12 15:13 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-04 7:43 [Bug c++/99377] New: " boris at kolpackov dot net 2021-03-04 18:38 ` [Bug c++/99377] " nathan at gcc dot gnu.org 2021-03-05 17:11 ` nathan at gcc dot gnu.org 2021-03-05 19:55 ` cvs-commit at gcc dot gnu.org 2021-03-05 19:57 ` nathan at gcc dot gnu.org 2021-03-30 15:14 ` boris at kolpackov dot net 2021-11-29 22:05 ` johelegp at gmail dot com 2021-11-29 22:29 ` johelegp at gmail dot com 2021-12-20 18:35 ` johelegp at gmail dot com 2022-07-16 17:31 ` johelegp at gmail dot com 2022-07-16 17:32 ` johelegp at gmail dot com 2022-07-16 17:32 ` johelegp at gmail dot com 2022-07-16 17:32 ` johelegp at gmail dot com 2022-07-16 17:33 ` johelegp at gmail dot com 2022-07-17 16:21 ` johelegp at gmail dot com 2022-10-11 19:02 ` cvs-commit at gcc dot gnu.org 2022-10-12 15:13 ` ppalka at gcc dot gnu.org [this message] 2024-03-06 20:43 ` ppalka at gcc dot gnu.org 2024-04-10 0:42 ` cvs-commit at gcc dot gnu.org 2024-04-10 0:45 ` 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-99377-4-PnahWZNOpo@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).