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++/104618] [12 Regression] trunk 20220221 on x86_64-linux-gnu ICEs building sh.cc for sh4-linux-gnu (in build_call_a, at cp/call.cc:381)
Date: Mon, 07 Mar 2022 23:32:47 +0000 [thread overview]
Message-ID: <bug-104618-4-FtvvomuRwX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104618-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104618
--- Comment #5 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:03e0c807ef50684cc1d49144948aa409decb91f9
commit r12-7528-g03e0c807ef50684cc1d49144948aa409decb91f9
Author: Jason Merrill <jason@redhat.com>
Date: Mon Feb 28 12:05:34 2022 -0400
c++: tweak to (*(fn))() patch [PR104618]
Other callers of mark_single_function might also want to look through these
wrapapers.
PR c++/104618
gcc/cp/ChangeLog:
* decl2.cc (mark_single_function): Look through parens and location
wrapper.
* typeck.cc (cp_build_addr_expr_1): Not here.
next prev parent reply other threads:[~2022-03-07 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 19:22 [Bug target/104618] New: [12 Regression] trunk 20220221 on x86_64-linux-gnu ICEs building sh.cc for sh4-linux-gnu doko at debian dot org
2022-02-21 21:06 ` [Bug c++/104618] [12 Regression] trunk 20220221 on x86_64-linux-gnu ICEs building sh.cc for sh4-linux-gnu (in build_call_a, at cp/call.cc:381) pinskia at gcc dot gnu.org
2022-02-21 23:32 ` pinskia at gcc dot gnu.org
2022-02-22 0:29 ` pinskia at gcc dot gnu.org
2022-02-22 10:29 ` rguenth at gcc dot gnu.org
2022-02-25 19:21 ` jason at gcc dot gnu.org
2022-02-27 22:52 ` cvs-commit at gcc dot gnu.org
2022-03-02 20:57 ` mpolacek at gcc dot gnu.org
2022-03-07 23:32 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-08 3:59 ` jason 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-104618-4-FtvvomuRwX@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).