This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [C++ PATCH] Don't ICE on invalid decltype uses (PR c++/34271)

From: "Doug Gregor" <doug dot gregor at gmail dot com>
To: "Jakub Jelinek" <jakub at redhat dot com>
Cc: "Jason Merrill" <jason at redhat dot com>, "Mark Mitchell" <mark at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
Date: Tue, 4 Dec 2007 21:42:38 -0500
Subject: Re: [C++ PATCH] Don't ICE on invalid decltype uses (PR c++/34271)
References: <20071204192450.GF16835@devserv.devel.redhat.com> <24b520d20712041320j7b76e921rb4b41a0f7bc978a1@mail.gmail.com> <20071204215052.GH16835@devserv.devel.redhat.com>

On Dec 4, 2007 4:50 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> > I'd rather just handle SCOPE_REF in finish_decltype_type and print the
> > error at that point. As a general rule, we should diagnose whatever we
> > can when parsing the template. Sooner or later, we're going to have to
> > if we want to properly support C++0x concepts.
>
> Ok, here is the alternative patch, regtested on x86_64-linux:
>         PR c++/34271

This looks good to me, but I can't approve it.

  - Doug

References:
- [C++ PATCH] Don't ICE on invalid decltype uses (PR c++/34271)
  - From: Jakub Jelinek
- Re: [C++ PATCH] Don't ICE on invalid decltype uses (PR c++/34271)
  - From: Doug Gregor
- Re: [C++ PATCH] Don't ICE on invalid decltype uses (PR c++/34271)
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]