public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57] [DR 325] GCC can't parse a non-parenthesized comma in a template-id within a default argument
Date: Sun, 25 Jul 2021 02:53:31 +0000 [thread overview]
Message-ID: <bug-57-4-gKxr2RK2Zp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #47 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Paolo Carlini from comment #45)
> (In reply to comment #44)
> > GCC 4.4 came and went. Now what?
>
> Now what what? The issue is fixed for 4.4, and I just double checked myself
> the original testcase and the one in Comment #40, both compile fine.
> Comments #38 and #39 explain why technically the PR must remain suspended
> for now. So?
Yeah, can this be closed?
next parent reply other threads:[~2021-07-25 2:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-57-4@http.gcc.gnu.org/bugzilla/>
2021-07-25 2:53 ` egallager at gcc dot gnu.org [this message]
2021-07-26 9:19 ` redi at gcc dot gnu.org
2021-12-04 11:49 ` pinskia at gcc dot gnu.org
[not found] <bug-57-797@http.gcc.gnu.org/bugzilla/>
2005-11-06 4:38 ` pinskia at gcc dot gnu dot org
2006-04-05 1:57 ` pinskia at gcc dot gnu dot org
2006-09-14 15:00 ` pinskia at gcc dot gnu dot org
2006-12-04 22:51 ` pinskia at gcc dot gnu dot org
2007-01-01 19:02 ` pinskia at gcc dot gnu dot org
2007-10-12 18:31 ` pcarlini at suse dot de
2007-10-24 15:46 ` jason at gcc dot gnu dot org
2007-10-24 19:48 ` jason at gcc dot gnu dot org
2008-04-28 20:45 ` jason at gcc dot gnu dot org
2008-08-10 16:03 ` manu at gcc dot gnu dot org
2008-08-10 18:23 ` pinskia at gmail dot com
2008-08-10 18:32 ` manu at gcc dot gnu dot org
2009-01-06 6:03 ` zerger at gmail dot com
2009-01-06 15:46 ` bangerth at dealii dot org
2009-03-10 23:01 ` pinskia at gcc dot gnu dot org
2009-04-28 16:52 ` pinskia at gcc dot gnu dot org
2009-09-01 22:11 ` keith dot g dot erickson at lmco dot com
2009-09-01 22:26 ` paolo dot carlini at oracle dot com
2009-12-23 7:09 ` sodiumgood at gmail dot com
[not found] <20000305032601.57.martin@loewis.home.cs.tu-berlin.de>
2004-04-29 14:48 ` bangerth at dealii dot org
2004-04-30 1:46 ` pinskia at gcc dot gnu dot org
2004-04-30 2:54 ` igodard at pacbell dot net
2004-04-30 14:50 ` bangerth at ices dot utexas dot edu
2004-04-30 16:44 ` llewelly
2004-04-30 16:44 ` llewelly at xmission dot com
2004-04-30 17:07 ` sebor at roguewave dot com
2004-04-30 20:13 ` igodard at pacbell dot net
2004-06-13 22:55 ` pinskia at gcc dot gnu dot org
2004-06-22 2:15 ` bje at gcc dot gnu dot org
2004-06-22 2:54 ` pinskia at gcc dot gnu dot org
2004-11-27 15:10 ` pinskia at gcc dot gnu dot org
2004-11-27 16:04 ` prez at neuromancy dot net
2004-11-29 9:26 ` nathan at gcc dot gnu dot org
2005-04-06 14:10 ` liu_gw at 163 dot com
2005-04-06 15:18 ` pinskia at gcc dot gnu dot org
2005-04-18 18:42 ` pinskia at gcc dot gnu dot 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-57-4-gKxr2RK2Zp@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).