public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markmigm at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106820] internal compiler error: in function_and_variable_visibility [for std::shared_ptr<data>{b,??} use via <memory> module]
Date: Mon, 05 Sep 2022 08:01:20 +0000	[thread overview]
Message-ID: <bug-106820-4-ni4F257EbQ@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

Mark Millard <markmigm at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|internal compiler error: in |internal compiler error: in
                   |function_and_variable_visib |function_and_variable_visib
                   |ility [for                  |ility [for
                   |std::dynamic_pointer_cast   |std::shared_ptr<data>{b,??}
                   |use via <memory> module]    |use via <memory> module]

--- Comment #2 from Mark Millard <markmigm at gmail dot com> ---
I've produced a more reduced example source:

import <memory>;

struct data
{
        virtual ~data() = default;
};

auto test(std::shared_ptr<data> b)
{
        return std::shared_ptr<data>{b,nullptr};
}


nullptr is not special here: other alternative raw pointers also get
the "internal compiler error: in function_and_variable_visibility"
notice. nullptr is just the simplest example.

Using a #include instead also gets the error (as expected) --unless
the -fmodules-ts command line option is then omitted. -fmodules-ts
is important to getting the message in the FreeBSD lang/gcc12 context.

  parent reply	other threads:[~2022-09-05  8:01 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 " markmigm at gmail dot com
2022-09-03 20:56 ` [Bug c++/106820] " markmigm at gmail dot com
2022-09-05  8:01 ` markmigm at gmail dot com [this message]
2022-09-07 20:10 ` [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: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
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-ni4F257EbQ@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).