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++/104470] [10/11/12/13 Regression] internal compiler error: Segmentation fault compiling std::variant with -std=c++20 Date: Fri, 29 Apr 2022 21:25:04 +0000 [thread overview] Message-ID: <bug-104470-4-CRbAUiC2vg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104470-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104470 --- Comment #6 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:4259c229b457361a9b5cdec157e058bf0c2c8b77 commit r13-54-g4259c229b457361a9b5cdec157e058bf0c2c8b77 Author: Jason Merrill <jason@redhat.com> Date: Wed Apr 27 11:13:24 2022 -0400 c++: alias CTAD and member alias templates [PR104470] In this testcase, we were trying to substitute into variant<Foo<T>>::__accepted_type, but failed to look it up because variant<Foo<T>> doesn't exist. In other cases we already rewrite such things into a dependent reference; we need to do that for alias templates as well. This caused some testsuite regressions on alias uses outside of deduction guides, so I've made all of this rewriting conditional on a new tf_dguide tsubst flag. PR c++/104470 gcc/cp/ChangeLog: * cp-tree.h (enum tsubst_flags): Add tf_dguide. * pt.cc (tsubst_aggr_type): Check it. (tsubst_baselink, tsubst_copy): Check it. (maybe_dependent_member_ref): Check it. (instantiate_alias_template): Handle it. (build_deduction_guide): Set it. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/explicit11.C: Second example also ill-formed. * g++.dg/cpp2a/class-deduction-alias12.C: New test.
next prev parent reply other threads:[~2022-04-29 21:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-09 18:25 [Bug c++/104470] New: " serpent7776 at gmail dot com 2022-02-10 1:09 ` [Bug c++/104470] " pinskia at gcc dot gnu.org 2022-02-10 6:02 ` pinskia at gcc dot gnu.org 2022-02-10 8:18 ` pinskia at gcc dot gnu.org 2022-04-22 11:57 ` max.kanold@nu-cost.com 2022-04-22 15:03 ` mpolacek at gcc dot gnu.org 2022-04-22 15:10 ` [Bug c++/104470] [10/11/12 Regression] " mpolacek at gcc dot gnu.org 2022-04-26 22:34 ` jason at gcc dot gnu.org 2022-04-29 21:25 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-04 21:59 ` [Bug c++/104470] [10/11/12/13 " cvs-commit at gcc dot gnu.org 2022-05-15 16:29 ` [Bug c++/104470] [10/11/12 " cvs-commit at gcc dot gnu.org 2022-06-28 10:48 ` [Bug c++/104470] [10/11 " jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug c++/104470] [11 " rguenth 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-104470-4-CRbAUiC2vg@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).