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++/110809] ICE: in unify, at cp/pt.cc:25226 with floating-point NTTPs
Date: Wed, 26 Jul 2023 05:38:06 +0000 [thread overview]
Message-ID: <bug-110809-4-o97U4KL7Kr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110809-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110809
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Ed Catmur from comment #5)
> The original code is valid. A reduced valid case would be:
> ```
> template <double> struct S {};
> template <typename Hash, int i> struct bucket {};
> template <typename Hash, int i>
> int find_indices_impl(bucket<Hash, i> const &);
> struct HashTable : bucket<S<1.>, 1>, bucket<S<2.>, 2> {};
> auto t = find_indices_impl<S<1.>>(HashTable{});
> ```
Oh yes and yes the above looks like the original code even.
It is definitely trying to match bucket<S<2.>, 2> base class with bucket<S<1.>,
i> though and it is ICEing there.
next prev parent reply other threads:[~2023-07-26 5:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 18:58 [Bug c++/110809] New: " ed at catmur dot uk
2023-07-25 19:04 ` [Bug c++/110809] " mpolacek at gcc dot gnu.org
2023-07-25 22:34 ` pinskia at gcc dot gnu.org
2023-07-26 5:04 ` pinskia at gcc dot gnu.org
2023-07-26 5:06 ` pinskia at gcc dot gnu.org
2023-07-26 5:29 ` ed at catmur dot uk
2023-07-26 5:38 ` pinskia at gcc dot gnu.org [this message]
2023-07-26 14:18 ` ppalka at gcc dot gnu.org
2023-07-26 20:52 ` cvs-commit at gcc dot gnu.org
2023-07-26 20:53 ` ppalka at gcc dot gnu.org
2023-07-27 14:35 ` cvs-commit at gcc dot gnu.org
2024-01-24 16:32 ` 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-110809-4-o97U4KL7Kr@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).