public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106820] [modules] internal compiler error: in function_and_variable_visibility [for std::shared_ptr<data>{b,??} use via <memory> header unit]: mishandling of "weak" usage generated via __gthrw(pthread_mutex_unlock) use
Date: Wed, 12 Oct 2022 09:44:44 +0000 [thread overview]
Message-ID: <bug-106820-4-HXslK6InRQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106820-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106820
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Keywords| |visibility
Last reconfirmed| |2022-10-12
Status|UNCONFIRMED |NEW
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> I think I should be able to reproduce this on linux with an older glibc, or
> with libstdc++ modified to use weak symbols again. Trying that now ...
Confirmed. The ICE is still present on trunk.
next prev parent reply other threads:[~2022-10-12 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 20:48 [Bug c++/106820] New: internal compiler error: in function_and_variable_visibility [for std::dynamic_pointer_cast use via <memory> module] markmigm at gmail dot com
2022-09-03 20:56 ` [Bug c++/106820] " markmigm at gmail dot com
2022-09-05 8:01 ` [Bug c++/106820] internal compiler error: in function_and_variable_visibility [for std::shared_ptr<data>{b,??} " markmigm at gmail dot com
2022-09-07 20:10 ` markmigm at gmail dot com
2022-09-07 20:43 ` markmigm at gmail dot com
2022-09-07 22:21 ` [Bug c++/106820] [modules] internal compiler error: in function_and_variable_visibility [for std::shared_ptr<data>{b,??} use via <memory> header unit]: mishandling of "weak" usage generated via __gthrw(pthread_mutex_unlock) use markmigm at gmail dot com
2022-10-12 9:34 ` redi at gcc dot gnu.org
2022-10-12 9:36 ` redi at gcc dot gnu.org
2022-10-12 9:44 ` redi at gcc dot gnu.org [this message]
2022-10-12 14:29 ` ppalka at gcc dot gnu.org
2024-04-14 16:50 ` [Bug c++/106820] [modules] ICE in function_and_variable_visibility with modules and weakref ppalka at gcc dot gnu.org
2024-04-30 17:06 ` 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-106820-4-HXslK6InRQ@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).