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++/105921] internal compiler error: in cp_parser_template_id, at cp/parser.cc:18362
Date: Tue, 21 Jun 2022 02:55:47 +0000	[thread overview]
Message-ID: <bug-105921-4-5Ncl3tLmg6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105921-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |11.1.0, 6.1.0, 9.1.0
           Keywords|ice-on-valid-code           |

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Reduced testcase:
template <int T>
auto a = (struct A {}){};

int main () {
    a<4>;
}

So GCC declares this as a compound literal where the new type is defined in the
(). It turns out for template variables, GCC is not ready for this.

Note clang rejects this code in both the non-template case and the template
case where defining a new struct is not allowed.

I don't know if we should restrict defining the new struct here or not.

This is not a regression either.

      parent reply	other threads:[~2022-06-21  2:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 19:54 [Bug c++/105921] New: " orbisvicis+gcc at gmail dot com
2022-06-10 19:58 ` [Bug c++/105921] " orbisvicis+gcc at gmail dot com
2022-06-16 13:17 ` marxin at gcc dot gnu.org
2022-06-21  2:55 ` 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-105921-4-5Ncl3tLmg6@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).