public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aaron at aaronballman dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101209] New: ICE with trailing return type on a conversion operator Date: Fri, 25 Jun 2021 11:31:05 +0000 [thread overview] Message-ID: <bug-101209-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101209 Bug ID: 101209 Summary: ICE with trailing return type on a conversion operator Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: aaron at aaronballman dot com Target Milestone: --- I was curious what kind of diagnostics different compilers would give me for some nonsense code, and found that the following code causes an ICE in GCC. struct S { operator int() const -> double; }; <source>:2:27: internal compiler error: in splice_late_return_type, at cp/pt.c:29753 2 | operator int() const -> double; | ^~~~~~ 0x1d48999 internal_error(char const*, ...) ???:0 0x724013 fancy_abort(char const*, int, char const*) ???:0 0x9847fc splice_late_return_type(tree_node*, tree_node*) ???:0 0x808c53 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*, decl_context, int, tree_node**) ???:0 0x834403 grokfield(cp_declarator const*, cp_decl_specifier_seq*, tree_node*, bool, tree_node*, tree_node*) ???:0 0x94cadd c_parse_file() ???:0 0xacfe82 c_common_parse_file() ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Compiler returned: 1 This should likely give an error about using a trailing return type for a function with a declared return type other than a placeholder type.
next reply other threads:[~2021-06-25 11:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-25 11:31 aaron at aaronballman dot com [this message] 2021-06-25 11:41 ` [Bug c++/101209] " aaron at aaronballman dot com 2021-08-07 21:29 ` [Bug c++/101209] [10/11/12 Regression] " pinskia at gcc dot gnu.org 2021-09-27 22:13 ` pinskia at gcc dot gnu.org 2021-09-27 22:16 ` 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-101209-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: linkBe 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).