From: "Doug Gregor" <doug.gregor@gmail.com>
To: "Jakub Jelinek" <jakub@redhat.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] Handle TYPE_PACK_EXPANSION return in tsubst_exception_specification
Date: Mon, 19 Nov 2007 16:43:00 -0000 [thread overview]
Message-ID: <24b520d20711190535u350daedcu230de69a864e564e@mail.gmail.com> (raw)
In-Reply-To: <20071118200131.GF5451@devserv.devel.redhat.com>
On Nov 18, 2007 3:01 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> > 2007-11-18 Douglas Gregor <doug.gregor@gmail.com>
> >
> > PR c++/33509
> > * g++.dg/cpp0x/variadic-throw.C: New.
>
> I think it would be good to add not only this valid testcase, but
> the invalid one as well (i.e. one with
> return S<0, 1, 2>::foo<0, 1> ();
> rather than
> return S<0, 1, 2>::foo<0, 1, 3> ();
> ) to make sure it doesn't ICE and issues some meaningful error
> on invalid code.
Okay, will do.
- Doug
next prev parent reply other threads:[~2007-11-19 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 15:46 Doug Gregor
2007-11-18 21:51 ` Jakub Jelinek
2007-11-19 16:43 ` Doug Gregor [this message]
2007-12-03 21:39 ` Jason Merrill
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=24b520d20711190535u350daedcu230de69a864e564e@mail.gmail.com \
--to=doug.gregor@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).