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++/103752] [12 Regression][ICE][modules] with import <string>
Date: Wed, 09 Feb 2022 15:41:24 +0000 [thread overview]
Message-ID: <bug-103752-4-97bk0ZotxZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103752-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103752
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:1ce5395977f37e8d0c03394f7b932a584ce85cc7
commit r12-7133-g1ce5395977f37e8d0c03394f7b932a584ce85cc7
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 9 00:31:12 2022 -0500
c++: modules and explicit(bool) [PR103752]
We weren't streaming a C++20 dependent explicit-specifier.
PR c++/103752
gcc/cp/ChangeLog:
* module.cc (trees_out::core_vals): Stream explicit specifier.
(trees_in::core_vals): Likewise.
* pt.cc (store_explicit_specifier): No longer static.
(tsubst_function_decl): Clear DECL_HAS_DEPENDENT_EXPLICIT_SPEC_P.
* cp-tree.h (lookup_explicit_specifier): Declare.
gcc/testsuite/ChangeLog:
* g++.dg/modules/explicit-bool-1_b.C: New test.
* g++.dg/modules/explicit-bool-1_a.H: New test.
next prev parent reply other threads:[~2022-02-09 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 17:14 [Bug c++/103752] New: " egor.pugin at gmail dot com
2021-12-16 21:14 ` [Bug c++/103752] " pinskia at gcc dot gnu.org
2022-01-17 12:53 ` rguenth at gcc dot gnu.org
2022-01-17 13:13 ` redi at gcc dot gnu.org
2022-02-09 2:25 ` jason at gcc dot gnu.org
2022-02-09 15:41 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-09 15:41 ` jason at gcc dot gnu.org
2022-02-09 15:45 ` johelegp at gmail dot com
2022-02-09 16:32 ` johelegp at gmail dot com
2022-10-12 11:31 ` redi 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-103752-4-97bk0ZotxZ@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).