public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99377] [modules] undefined std::string_view::empty() if referenced in inline exported function
Date: Fri, 05 Mar 2021 19:55:50 +0000	[thread overview]
Message-ID: <bug-99377-4-qGoVWn8lYF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99377-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:

https://gcc.gnu.org/g:1e5cdb9f896fb220b26fd2080406504c4badf5af

commit r11-7530-g1e5cdb9f896fb220b26fd2080406504c4badf5af
Author: Nathan Sidwell <nathan@acm.org>
Date:   Fri Mar 5 10:34:23 2021 -0800

    c++: Local instantiations of imported specializations [PR 99377]

    This turned out to be the function version of the previous fix.  We
    can import an implicit specialization declaration that we need to
    instantiate.  We must mark the instantiation so we remember to stream
    it.

            PR c++/99377
            gcc/cp/
            * pt.c (instantiate_decl): Call set_instantiating_module.
            gcc/testsuite/
            * g++.dg/modules/pr99377_a.H: New.
            * g++.dg/modules/pr99377_b.C: New.
            * g++.dg/modules/pr99377_c.C: New.

  parent reply	other threads:[~2021-03-05 19:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  7:43 [Bug c++/99377] New: " boris at kolpackov dot net
2021-03-04 18:38 ` [Bug c++/99377] " nathan at gcc dot gnu.org
2021-03-05 17:11 ` nathan at gcc dot gnu.org
2021-03-05 19:55 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-05 19:57 ` nathan at gcc dot gnu.org
2021-03-30 15:14 ` boris at kolpackov dot net
2021-11-29 22:05 ` johelegp at gmail dot com
2021-11-29 22:29 ` johelegp at gmail dot com
2021-12-20 18:35 ` johelegp at gmail dot com
2022-07-16 17:31 ` johelegp at gmail dot com
2022-07-16 17:32 ` johelegp at gmail dot com
2022-07-16 17:32 ` johelegp at gmail dot com
2022-07-16 17:32 ` johelegp at gmail dot com
2022-07-16 17:33 ` johelegp at gmail dot com
2022-07-17 16:21 ` johelegp at gmail dot com
2022-10-11 19:02 ` cvs-commit at gcc dot gnu.org
2022-10-12 15:13 ` ppalka at gcc dot gnu.org
2024-03-06 20:43 ` ppalka at gcc dot gnu.org
2024-04-10  0:42 ` cvs-commit at gcc dot gnu.org
2024-04-10  0:45 ` 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-99377-4-qGoVWn8lYF@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).