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: Wed, 04 May 2022 21:59:58 +0000 [thread overview] Message-ID: <bug-104470-4-zO40YNDL3z@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 #7 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:a47ab705c2c9f07f08fde499d6be4682efe4b626 commit r13-124-ga47ab705c2c9f07f08fde499d6be4682efe4b626 Author: Jason Merrill <jason@redhat.com> Date: Tue Apr 26 18:32:51 2022 -0400 c++: alias CTAD refactoring [PR104470] In my previous PR104470 patch I added yet another place that needs to handle dependent member rewriting for deduction guides; this patches centralizes rewriting into maybe_dependent_member_ref. tsubst_baselink still has its own handling because that's simpler than teaching maybe_dependent_member_ref about BASELINKs. PR c++/104470 gcc/cp/ChangeLog: * pt.cc (maybe_dependent_member_ref): Handle types. (tsubst, tsubst_copy): Use it. (tsubst_aggr_type, instantiate_alias_template): Don't handle tf_dguide here.
next prev parent reply other threads:[~2022-05-04 21:59 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 ` [Bug c++/104470] [10/11/12/13 " cvs-commit at gcc dot gnu.org 2022-05-04 21:59 ` cvs-commit at gcc dot gnu.org [this message] 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-zO40YNDL3z@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).