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++/100583] [modules] ICE when importing <span> Date: Wed, 12 Oct 2022 11:31:59 +0000 [thread overview] Message-ID: <bug-100583-4-mWvA7VW3Kd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100583-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100583 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.0 Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- Fixed by commit r12-7133-g1ce5395977f37e 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. *** This bug has been marked as a duplicate of bug 103752 ***
prev parent reply other threads:[~2022-10-12 11:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-13 11:12 [Bug libstdc++/100583] New: " andreemalcher at gmail dot com 2021-09-27 2:28 ` [Bug c++/100583] " johelegp at gmail dot com 2021-09-28 15:54 ` redi at gcc dot gnu.org 2021-10-03 15:11 ` johelegp at gmail dot com 2021-11-12 18:58 ` johelegp at gmail dot com 2022-02-13 14:16 ` johelegp at gmail dot com 2022-10-12 11:31 ` redi at gcc dot gnu.org [this message]
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-100583-4-mWvA7VW3Kd@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).