public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98662] [10/11/12/13 Regression] checking ICE in friend_accessible_p since r227023
Date: Wed, 19 Oct 2022 09:26:24 +0000	[thread overview]
Message-ID: <bug-98662-4-5mPLu4AI65@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98662-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98662

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
So is this a rejects-valid as well?  The assert suggests the return value and
the diagnostic without checking is wrong:

> g++-11 t.C -c
t.C: In instantiation of 'int f(S<int>)':
t.C:16:10:   required from here
t.C:6:14: error: 'int S<const int>::j' is protected within this context
    6 |     (void) y.j;
      |            ~~^
t.C:12:7: note: declared protected here
   12 |   int j;
      |       ^

  parent reply	other threads:[~2022-10-19  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 20:40 [Bug c++/98662] New: " ppalka at gcc dot gnu.org
2021-01-14  8:22 ` [Bug c++/98662] " marxin at gcc dot gnu.org
2021-12-23  9:48 ` pinskia at gcc dot gnu.org
2021-12-23 11:59 ` marxin at gcc dot gnu.org
2022-05-17 18:22 ` [Bug c++/98662] [9/10/11/12/13 Regression] " ppalka at gcc dot gnu.org
2022-05-27  9:44 ` [Bug c++/98662] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2022-07-26 13:45 ` rguenth at gcc dot gnu.org
2022-10-19  9:26 ` rguenth at gcc dot gnu.org [this message]
2022-12-20 13:30 ` rguenth at gcc dot gnu.org
2023-07-07 10:38 ` [Bug c++/98662] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-11  2:40 ` [Bug c++/98662] [11/12/13 " law 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-98662-4-5mPLu4AI65@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).