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++/113620] ICE with inner class template speciailization and depdent NSDMI
Date: Fri, 26 Jan 2024 18:39:14 +0000	[thread overview]
Message-ID: <bug-113620-4-hnd4Yaf1BB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113620-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113620

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #5)
> Seems to be a name lookup issue ultimately:
> 
> struct A {
>   template<class T, class U>
>   struct B;
> 
>   template<class V>
>   struct B<int, V> {
>     int x = V::value; // error: 'V' has not been declared
>     int y = T::value; // no error!
>     int z = U::value; // no error!
>   };
> };

That would make sense on why it was rejected before GCC 4.9 even.

Now I wonder if this is related to the diagnostic issue mentioned in
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643811.html even.

      parent reply	other threads:[~2024-01-26 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 15:10 [Bug c++/113620] New: Specialized Template hans.buchmann.wantuch at gmail dot com
2024-01-26 15:37 ` [Bug c++/113620] " xry111 at gcc dot gnu.org
2024-01-26 16:58 ` [Bug c++/113620] ICE with missing "typename" and -std=c++20 pinskia at gcc dot gnu.org
2024-01-26 16:59 ` pinskia at gcc dot gnu.org
2024-01-26 17:11 ` [Bug c++/113620] ICE with inner class template speciailization and depdent NSDMI pinskia at gcc dot gnu.org
2024-01-26 18:04 ` ppalka at gcc dot gnu.org
2024-01-26 18:39 ` 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-113620-4-hnd4Yaf1BB@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).