public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107623] Using a parameter pack twice results in ambiguous overloaded function.
Date: Thu, 10 Nov 2022 20:33:15 +0000 [thread overview]
Message-ID: <bug-107623-4-vM5OBvjAZn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107623-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107623
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
On the trunk (with --enable-checking=yes) we get an ICE:
<source>: In function 'int main()':
<source>:10:11: internal compiler error: in comptypes, at cp/typeck.cc:1684
10 | test(f, 1);
| ~~~~^~~~~~
0x23961de internal_error(char const*, ...)
???:0
0xaaa542 fancy_abort(char const*, int, char const*)
???:0
0xce0f15 more_specialized_fn(tree_node*, tree_node*, int)
???:0
0xad8609 build_new_function_call(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, int)
???:0
0xd01048 finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
???:0
0xc88297 c_parse_file()
???:0
0xdd1699 c_common_parse_file()
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See https://gcc.gnu.org/bugs/ for instructions.
ASM generation compiler returned: 1
prev parent reply other threads:[~2022-11-10 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 20:15 [Bug c++/107623] New: " jlaros at fixedpoint dot nl
2022-11-10 20:33 ` pinskia at gcc dot gnu.org [this message]
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-107623-4-vM5OBvjAZn@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).