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 07:58:26 +0000	[thread overview]
Message-ID: <bug-113498-4-LbWPiRimtj@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 #2 from Bob Miller <bobmiller at nvidia dot com> ---
Apologies, I should have reduced this test case further before submission, but
I was under the mistaken impression that the template weirdness was the cause.
I believe this is a minimized example: https://godbolt.org/z/s3vGEh4Wx

template<int d>
struct S_Base
{
    static constexpr int D = d;
};

template<int d>
struct S : public S_Base<d>
{
    using S_Base<d>::D;
    constexpr void f() const
        requires(D > 0) {}

};

int main(int, char**)
{
    S<1> s;
    s.f();
    return 0;
}

  parent reply	other threads:[~2024-01-19  7:58 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 ` [Bug c++/113498] " bobmiller at nvidia dot com
2024-01-19  7:58 ` bobmiller at nvidia dot com [this message]
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-LbWPiRimtj@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).