public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lhlaurini at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104433] [modules] Importing <memory> and using std::make_shared causes linker errors Date: Tue, 11 Oct 2022 18:50:47 +0000 [thread overview] Message-ID: <bug-104433-4-3Uu8OP5EtJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104433-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104433 --- Comment #3 from Luiz Henrique Laurini <lhlaurini at hotmail dot com> --- Thank you for the fix. The test case seems to be working as expected now. However, the original code import <memory>; int main() { std::make_shared<int>(); } now causes an internal compiler error: during IPA pass: visibility main.cpp:6:1: internal compiler error: in function_and_variable_visibility, at ipa-visibility.cc:712 6 | } | ^ 0x236019e internal_error(char const*, ...) ???:0 0xaa1f68 fancy_abort(char const*, int, char const*) ???:0 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Godbolt link (using gcc trunk): https://godbolt.org/z/bMYYvWd8e Should I report a new bug?
next prev parent reply other threads:[~2022-10-11 18:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-07 20:17 [Bug c++/104433] New: " lhlaurini at hotmail dot com 2022-10-06 14:54 ` [Bug c++/104433] " ppalka at gcc dot gnu.org 2022-10-07 13:33 ` cvs-commit at gcc dot gnu.org 2022-10-07 13:36 ` ppalka at gcc dot gnu.org 2022-10-11 18:50 ` lhlaurini at hotmail dot com [this message] 2022-10-12 9:25 ` redi at gcc dot gnu.org 2022-10-12 19:13 ` 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-104433-4-3Uu8OP5EtJ@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).