public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bobmiller at nvidia dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113498] ICE in GCC trunk: tree check: have using_decl in get_template_info, at cp/pt.cc:357 Date: Fri, 19 Jan 2024 06:44:20 +0000 [thread overview] Message-ID: <bug-113498-4-mgHVuB62ZA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113498-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113498 --- Comment #1 from Bob Miller <bobmiller at nvidia dot com> --- Bug also occurs on GCC Trunk in Compiler Explorer. Small test case to reproduce bug: https://godbolt.org/z/TorE88bMT #include <cstdlib> template<template<typename, size_t...> class ThisTT, typename T, size_t...Dims> struct S_Base { static constexpr size_t D = (Dims *...); }; template<template<typename, size_t...> class ThisTT, typename T, size_t...Dims> struct S : public S_Base<ThisTT, T, Dims...> { using S_Base<ThisTT, T, Dims...>::D; constexpr ThisTT<T, Dims...> f() const requires(D > 0) {return {};} }; template<typename T, size_t M, size_t N> struct S2 : public S<S2, T, M, N> { }; int main(int, char**) { S2<int, 1, 1> s2; s2.f(); return 0; }
next prev parent reply other threads:[~2024-01-19 6:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 6:35 [Bug c++/113498] New: " bobmiller at nvidia dot com 2024-01-19 6:44 ` bobmiller at nvidia dot com [this message] 2024-01-19 7:58 ` [Bug c++/113498] " bobmiller at nvidia dot com 2024-01-19 9:19 ` [Bug c++/113498] [14 regression] " rguenth at gcc dot gnu.org 2024-01-19 16:15 ` [Bug c++/113498] [14 regression] ICE in GCC trunk: tree check: have using_decl in get_template_info, at cp/pt.cc:357 since r14-6064 jakub at gcc dot gnu.org 2024-01-19 17:01 ` jason at gcc dot gnu.org 2024-01-19 19:23 ` cvs-commit at gcc dot gnu.org 2024-01-19 19:24 ` jason 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-113498-4-mgHVuB62ZA@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).