From: Sergei Trofimovich <slyfox@gentoo.org>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Sergei Trofimovich <siarheit@google.com>,
Martin Sebor <msebor@gcc.gnu.org>
Subject: Re: [PATCH] c++: suppress all warnings on memper pointers to work around dICE [PR101219]
Date: Fri, 23 Jul 2021 22:32:15 +0100 [thread overview]
Message-ID: <20210723223215.3f451dc4@zn3> (raw)
In-Reply-To: <387e2a61-a895-733d-5418-7c8c38d6f998@gmail.com>
On Fri, 23 Jul 2021 10:33:09 -0600
Jeff Law <jeffreyalaw@gmail.com> wrote:
> On 7/22/2021 5:15 PM, Sergei Trofimovich via Gcc-patches wrote:
> > From: Sergei Trofimovich <siarheit@google.com>
> >
> > r12-1804 ("cp: add support for per-location warning groups.") among other
> > things removed warning suppression from a few places including ptrmemfuncs.
> >
> > Currently ptrmemfuncs don't have valid BINFO attached which causes ICEs
> > in access checks:
> >
> > crash_signal
> > gcc/toplev.c:328
> > perform_or_defer_access_check(tree_node*, tree_node*, tree_node*, int, access_failure_info*)
> > gcc/cp/semantics.c:490
> > finish_non_static_data_member(tree_node*, tree_node*, tree_node*)
> > gcc/cp/semantics.c:2208
> > ...
> >
> > The change suppresses warnings again until we provide BINFOs for ptrmemfuncs.
> >
> > PR c++/101219
> >
> > gcc/cp/ChangeLog:
> >
> > * typeck.c (build_ptrmemfunc_access_expr): Suppress all warnings
> > to avoid ICE.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * g++.dg/torture/pr101219.C: New test.
> The C++ maintainers have the final say here, but ISTM that warning
> suppression shouldn't be used to avoid an ICE, even an ICE within the
> warning or diagnostic code itself.
Sounds good. I agree fixing it correctly is preferable and should improve
diagnostic on this very test case compared to gcc-11.
I'll need some help plumbing TYPE_BINFO() around build_ptrmemfunc_type().
My attempts to use `xref_basetypes (t, NULL_TREE);` to derive it for a
fresh expression only shuffles ICEs around.
--
Sergei
next prev parent reply other threads:[~2021-07-23 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 23:15 Sergei Trofimovich
2021-07-23 16:33 ` Jeff Law
2021-07-23 21:32 ` Sergei Trofimovich [this message]
2021-07-29 15:41 ` Jason Merrill
2021-08-06 15:34 ` Sergei Trofimovich
2021-08-11 19:19 ` Jason Merrill
2021-08-11 22:36 ` Sergei Trofimovich
2021-08-12 14:38 ` Jason Merrill
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=20210723223215.3f451dc4@zn3 \
--to=slyfox@gentoo.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=msebor@gcc.gnu.org \
--cc=siarheit@google.com \
/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).