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++/99869] [11 Regression] ICE: in do_auto_deduction, at cp/pt.c:29620 Date: Fri, 02 Apr 2021 23:57:58 +0000 [thread overview] Message-ID: <bug-99869-4-BXcH9R98Hj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99869-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99869 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:260caabe10cde0158b87968a3bac85575301dafa commit r11-7963-g260caabe10cde0158b87968a3bac85575301dafa Author: Patrick Palka <ppalka@redhat.com> Date: Fri Apr 2 19:46:24 2021 -0400 c++: placeholder type constraint inside range-for [PR99869] In the testcase below, during ahead-of-time deduction of a constrained auto inside a range-based for loop, we trip over an assert within do_auto_deduction which expects the deduction context to be adc_return_type or adc_variable_type, but do_range_for_auto_deduction calls do_auto_deduction with the context defaulted to adc_unspecified. We could safely relax the assert to also accept adc_unspecified, but it seems the deduction context should really be adc_variable_type here. gcc/cp/ChangeLog: PR c++/99869 * parser.c (do_range_for_auto_deduction): Pass adc_variable_type to do_auto_deduction. gcc/testsuite/ChangeLog: PR c++/99869 * g++.dg/cpp2a/concepts-placeholder6.C: New test.
next prev parent reply other threads:[~2021-04-02 23:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 15:38 [Bug c++/99869] New: " hewillk at gmail dot com 2021-04-01 18:31 ` [Bug c++/99869] [11 Regression] " mpolacek at gcc dot gnu.org 2021-04-01 18:32 ` mpolacek at gcc dot gnu.org 2021-04-01 18:35 ` ppalka at gcc dot gnu.org 2021-04-02 23:57 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-05 13:42 ` ppalka 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-99869-4-BXcH9R98Hj@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).