public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cooky.ykooc922 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113389] New: ICE when explicit object parameter is not declared as the first parameter
Date: Sun, 14 Jan 2024 17:14:28 +0000 [thread overview]
Message-ID: <bug-113389-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113389
Bug ID: 113389
Summary: ICE when explicit object parameter is not declared as
the first parameter
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: cooky.ykooc922 at gmail dot com
Target Milestone: ---
Although it is obviously an error, it causes ICE:
struct A {
void foo(A, this A);
};
compiler output:
<source>:3:17: error: Only the first parameter of a member function can be
declared as an explicit object parameter
3 | void foo(A, this A);
| ^~~~~~
<source>:3:23: internal compiler error: Segmentation fault
3 | void foo(A, this A);
| ^
0x2640d5c internal_error(char const*, ...)
???:0
0xa78793 perform_implicit_conversion_flags(tree_node*, tree_node*, int, int)
???:0
0xb18083 check_default_argument(tree_node*, tree_node*, int)
???:0
0xb1861f grokparms(tree_node*, tree_node**)
???:0
0xb2caa1 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*,
decl_context, int, tree_node**)
???:0
0xb50ff3 grokfield(cp_declarator const*, cp_decl_specifier_seq*, tree_node*,
bool, tree_node*, tree_node*)
???:0
0xc5214a c_parse_file()
???:0
0xda5b49 c_common_parse_file()
???:0
godbolt link with -std=c++23: https://godbolt.org/z/Mxefo3nj6
next reply other threads:[~2024-01-14 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 17:14 cooky.ykooc922 at gmail dot com [this message]
2024-01-15 18:47 ` [Bug c++/113389] " mpolacek at gcc dot gnu.org
2024-01-17 23:23 ` mpolacek at gcc dot gnu.org
2024-01-18 14:12 ` cvs-commit at gcc dot gnu.org
2024-01-18 15:01 ` mpolacek at gcc dot gnu.org
2024-01-20 17:09 ` pinskia 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-113389-4@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).