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++/107484] [13 Regression] ICE: Segmentation fault (in decls_match)
Date: Fri, 24 Mar 2023 08:39:11 +0000 [thread overview]
Message-ID: <bug-107484-4-9fsQYasAAT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107484-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107484
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|ice-checking |accepts-invalid
Priority|P2 |P1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Also crashes with a release checking build:
> ./cc1plus -quiet t.ii
t.ii:5:52: internal compiler error: Segmentation fault
5 | friend void qualified_friend_no_match::f(double);
| ^
0xe2c7af crash_signal
/home/rguenther/src/trunk/gcc/toplev.cc:314
0x793c24 decls_match(tree_node*, tree_node*, bool)
/home/rguenther/src/trunk/gcc/cp/decl.cc:1075
0x7b6de6 find_last_decl
/home/rguenther/src/trunk/gcc/cp/decl2.cc:1630
since it's not error-recovery it's still P1.
Also crashes with
namespace qualified_friend_no_match {
void f(int);
template<typename T> void f(T*);
struct X {
friend void qualified_friend_no_match::f(double *);
};
}
which looks more valid to me, but I'm not a C++ expert (but clang++ 13 accepts
it - but that also accepts the original testcase).
next prev parent reply other threads:[~2023-03-24 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 2:57 [Bug c++/107484] New: " asolokha at gmx dot com
2022-11-01 4:00 ` [Bug c++/107484] " pinskia at gcc dot gnu.org
2022-11-05 10:34 ` rguenth at gcc dot gnu.org
2022-11-11 18:51 ` mpolacek at gcc dot gnu.org
2023-01-24 22:14 ` jason at gcc dot gnu.org
2023-03-24 8:39 ` rguenth at gcc dot gnu.org [this message]
2023-04-04 3:23 ` cvs-commit at gcc dot gnu.org
2023-04-04 3:23 ` 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-107484-4-9fsQYasAAT@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).