public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103341] New: ICE type of variable instantiation constrained on template parameter
Date: Sat, 20 Nov 2021 18:54:43 +0000 [thread overview]
Message-ID: <bug-103341-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103341
Bug ID: 103341
Summary: ICE type of variable instantiation constrained on
template parameter
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: johelegp at gmail dot com
CC: johelegp at gmail dot com
Target Milestone: ---
See https://godbolt.org/z/68GYeKqK4.
```C++
template<class, class> struct is_same { };
template<class T, class U> concept same_as = is_same<T, U>::value;
template<class T> inline constexpr same_as<T> auto trait_v{1};
using _ [[maybe_unused]] = decltype(trait_v<int>);
```
Output:
```
<source>: In instantiation of 'constexpr const auto [requires
::same_as<<placeholder>, T>] trait_v<int>':
<source>:4:37: required from here
<source>:3:52: internal compiler error: tree check: accessed elt 1 of
'tree_vec' with 0 elts in hash, at cp/constraint.cc:2503
3 | template<class T> inline constexpr same_as<T> auto trait_v{1};
| ^~~~~~~
0x206d4e9 internal_error(char const*, ...)
???:0
0x6da40c tree_vec_elt_check_failed(int, int, char const*, int, char const*)
???:0
0x85fca0 sat_hasher::hash(sat_entry*)
???:0
0x85aed7 satisfaction_cache::satisfaction_cache(tree_node*, tree_node*,
sat_info)
???:0
0x85f01a constraints_satisfied_p(tree_node*, tree_node*)
???:0
0xa3384b do_auto_deduction(tree_node*, tree_node*, tree_node*, int,
auto_deduction_context, tree_node*, int)
???:0
0x8d2c1d cp_finish_decl(tree_node*, tree_node*, bool, tree_node*, int)
???:0
0xa46987 instantiate_decl(tree_node*, bool, bool)
???:0
0x8e7c9e maybe_instantiate_decl(tree_node*)
???:0
0x8e9760 mark_used(tree_node*, int)
???:0
0xabe557 finish_id_expression(tree_node*, tree_node*, tree_node*, cp_id_kind*,
bool, bool, bool*, bool, bool, bool, bool, char const**, unsigned int)
???:0
0xa0cc65 c_parse_file()
???:0
0xb94bf2 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
```
next reply other threads:[~2021-11-20 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 18:54 johelegp at gmail dot com [this message]
2021-11-22 9:15 ` [Bug c++/103341] " rguenth at gcc dot gnu.org
2021-12-14 8:08 ` [Bug c++/103341] [10/11 Regression] " pinskia at gcc dot gnu.org
2021-12-14 8:09 ` [Bug c++/103341] [11/12 " pinskia at gcc dot gnu.org
2021-12-14 8:13 ` pinskia at gcc dot gnu.org
2022-01-17 12:55 ` rguenth at gcc dot gnu.org
2022-01-28 13:18 ` cvs-commit at gcc dot gnu.org
2022-01-28 13:30 ` [Bug c++/103341] [11 " ppalka at gcc dot gnu.org
2022-01-31 6:16 ` asolokha at gmx dot com
2022-01-31 16:28 ` ppalka at gcc dot gnu.org
2022-04-12 23:44 ` cvs-commit at gcc dot gnu.org
2022-04-12 23:47 ` ppalka 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-103341-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).