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++/91241] [9/10 Regression] internal compiler error: symtab_node::verify failed
Date: Fri, 13 May 2022 17:13:56 +0000 [thread overview]
Message-ID: <bug-91241-4-Mu9vj1eluM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91241-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91241
--- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:a86e0cadefe5a2469bb9872bb5b93017ccb23935
commit r10-10734-ga86e0cadefe5a2469bb9872bb5b93017ccb23935
Author: Jason Merrill <jason@redhat.com>
Date: Mon Apr 5 22:50:44 2021 -0400
c++: mangling of lambdas in default args [PR91241]
In this testcase, the parms remembered in LAMBDA_EXPR_EXTRA_SCOPE are no
longer the parms of the FUNCTION_DECL they have as their DECL_CONTEXT, so
we
were mangling both lambdas as parm #0. But since the parms are numbered
from right to left we don't need to need to find them in the FUNCTION_DECL,
we can measure their own DECL_CHAIN.
gcc/cp/ChangeLog:
PR c++/91241
* mangle.c (write_compact_number): Add sanity check.
(write_local_name): Use list_length for parm number.
gcc/testsuite/ChangeLog:
PR c++/91241
* g++.dg/abi/lambda-defarg1.C: New test.
next prev parent reply other threads:[~2022-05-13 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91241-4@http.gcc.gnu.org/bugzilla/>
2020-04-20 21:58 ` [Bug c++/91241] [8/9/10 " mpolacek at gcc dot gnu.org
2020-09-11 13:08 ` [Bug c++/91241] [8/9/10/11 " mpolacek at gcc dot gnu.org
2020-12-07 10:41 ` marxin at gcc dot gnu.org
2020-12-07 10:47 ` Jan Hubicka
2020-12-07 10:47 ` hubicka at ucw dot cz
2020-12-07 10:57 ` marxin at gcc dot gnu.org
2020-12-07 21:27 ` mpolacek at gcc dot gnu.org
2021-04-06 0:24 ` jason at gcc dot gnu.org
2021-04-06 4:13 ` cvs-commit at gcc dot gnu.org
2021-04-06 4:27 ` [Bug c++/91241] [8/9/10 " jason at gcc dot gnu.org
2021-04-21 18:30 ` mpolacek at gcc dot gnu.org
2021-05-14 9:52 ` [Bug c++/91241] [9/10 " jakub at gcc dot gnu.org
2021-06-01 8:14 ` rguenth at gcc dot gnu.org
2022-05-13 17:13 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-27 8:37 ` [Bug c++/91241] [9 " 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-91241-4-Mu9vj1eluM@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).