public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "john at johnmaddock dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105320] New: Use of shared_ptr within a type exported from a module results in spurious compiler error
Date: Wed, 20 Apr 2022 18:28:48 +0000	[thread overview]
Message-ID: <bug-105320-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105320
           Summary: Use of shared_ptr within a type exported from a module
                    results in spurious compiler error
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: john at johnmaddock dot co.uk
  Target Milestone: ---

Reduced test case:

module.cpp:
module;

#include <memory>

export module test_support;

export template <class T> struct pimpl
{
private:
   std::shared_ptr<T> data;
public:
   pimpl(const T& x) : data(new T(x)) {}
   pimpl() = default;
};


test_module.cpp:
import test_support;

int main()
{
   pimpl<int> p1, p2(3);
}

Compile with:
g++ -std=gnu++20 -fmodules-ts module.cpp test_module.cpp

Results in:
D:/compilers/msys64/mingw64/include/c++/11.2.0/bits/shared_ptr_base.h:1369:
confused by earlier errors, bailing out

Note that there were no earlier errors ! ;)

             reply	other threads:[~2022-04-20 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 18:28 john at johnmaddock dot co.uk [this message]
2024-03-06 21:52 ` [Bug c++/105320] " ppalka at gcc dot gnu.org
2024-03-06 21:53 ` ppalka at gcc dot gnu.org
2024-03-06 22:04 ` ppalka at gcc dot gnu.org
2024-04-30  6:23 ` cvs-commit at gcc dot gnu.org
2024-04-30  7:32 ` 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-105320-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).