public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickbegg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114229] New: [modules] duplicate symbols when including stl in submodule
Date: Mon, 04 Mar 2024 16:42:58 +0000	[thread overview]
Message-ID: <bug-114229-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114229

            Bug ID: 114229
           Summary: [modules] duplicate symbols when including stl in
                    submodule
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nickbegg at gmail dot com
  Target Milestone: ---

using the same test src code as PR113930 -

// submod.mpp

module;

#include <iostream>

export module modA:submod;

// modA.mpp

module;

export module modA;

export import :submod;

// main.cpp

#include <string>

import modA;

std::string test_func() {
    return "";
}

Note that this test code causes #113930 to check in a GCC debug build.
With a GCC release build, at link time numerous STL symbols become duplicated -

% /home/nick/inst/gcc-trunk-release/bin/g++ -freport-bug -g
CMakeFiles/moduleMin.dir/main.cpp.o CMakeFiles/moduleMin.dir/submod.mpp.o
CMakeFiles/moduleMin.dir/modA.mpp.o -o moduleMin

/usr/bin/ld: CMakeFiles/moduleMin.dir/modA.mpp.o:(.rodata+0x40): multiple
definition of `vtable for std::basic_ios<wchar_t, std::char_traits<wchar_t> >';
CMakeFiles/moduleMin.dir/main.cpp.o:(.rodata+0x950): first defined here
/usr/bin/ld: CMakeFiles/moduleMin.dir/modA.mpp.o:(.rodata+0x60): multiple
definition of `vtable for std::basic_ostream<wchar_t, std::char_traits<wchar_t>
>'; CMakeFiles/moduleMin.dir/main.cpp.o:(.rodata+0x8f0): first defined here
/usr/bin/ld: CMakeFiles/moduleMin.dir/modA.mpp.o:(.rodata+0xb0): multiple
definition of `VTT for std::basic_ostream<wchar_t, std::char_traits<wchar_t>
>'; CMakeFiles/moduleMin.dir/main.cpp.o:(.rodata+0x940): first defined here
/usr/bin/ld: CMakeFiles/moduleMin.dir/modA.mpp.o:(.rodata+0xc0): multiple
definition of `vtable for std::basic_istream<wchar_t, std::char_traits<wchar_t>
>'; CMakeFiles/moduleMin.dir/main.cpp.o:(.rodata+0x740): first defined here

[snip]

Note that #including <iostream> in both places (rather than string in main.cpp)
resolves the issue - Is the include guard mechanism failing?

             reply	other threads:[~2024-03-04 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 16:42 nickbegg at gmail dot com [this message]
2024-03-04 16:48 ` [Bug c++/114229] " nickbegg at gmail dot com
2024-03-05 19:52 ` ppalka at gcc dot gnu.org
2024-03-05 20:25 ` [Bug c++/114229] [modules] duplicate vtable " ppalka at gcc dot gnu.org
2024-03-07 22:02 ` cvs-commit at gcc dot gnu.org
2024-03-07 22:05 ` nshead at gcc dot gnu.org
2024-03-07 23:04 ` nickbegg at gmail dot com
2024-03-08 15:49 ` ppalka 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-114229-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: link
Be 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).