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++/59173] [10/11 Regression] Alias template in partial specialization finds name from primary template
Date: Mon, 02 Aug 2021 02:47:17 +0000	[thread overview]
Message-ID: <bug-59173-4-ki7HyEGtJB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59173-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |10.4
      Known to fail|                            |10.1.0, 4.8.5
            Summary|Alias template in partial   |[10/11 Regression] Alias
                   |specialization finds name   |template in partial
                   |from primary template       |specialization finds name
                   |                            |from primary template
      Known to work|                            |4.9.0, 7.5.0, 9.3.0, 9.4.0

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So this was fixed in 4.9 and then broke again in GCC 10 so it is a regression.

  parent reply	other threads:[~2021-08-02  2:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 13:34 [Bug c++/59173] New: " jhs at edg dot com
2013-11-18 14:43 ` [Bug c++/59173] " redi at gcc dot gnu.org
2013-11-18 14:44 ` paolo.carlini at oracle dot com
2013-11-20 13:40 ` redi at gcc dot gnu.org
2013-11-20 13:42 ` redi at gcc dot gnu.org
2021-08-02  2:47 ` pinskia at gcc dot gnu.org [this message]
2022-06-28 10:30 ` [Bug c++/59173] [10/11 Regression] " jakub at gcc dot gnu.org
2023-07-07  7:26 ` [Bug c++/59173] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-07  7:26 ` rguenth 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-59173-4-ki7HyEGtJB@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).