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]

Re: [PATCH] Avoid segfaulting in {start,finish}_decl

To: jakub at redhat dot com
Subject: Re: [PATCH] Avoid segfaulting in {start,finish}_decl
From: Jim Wilson <wilson at cygnus dot com>
Date: Sat, 21 Oct 2000 17:31:18 -0700
cc: gcc-patches at gcc dot gnu dot org
References: <20001020234609.I1188@sunsite.ms.mff.cuni.cz> <20001020163022.B14486@cygnus.com>

In article <20001021023205.G6207@devserv.devel.redhat.com> you write:
>while with Jim's patch it does not print the last error.
>So the question is whether we want to put that error (to stay consistent
>with previous releases) or not.

I deliberately disabled printing of that error message.  The program only
has one error, so it is wrong to print two error messages for it.

Jim

References:
- [PATCH] Avoid segfaulting in {start,finish}_decl
  - From: Jakub Jelinek
- Re: [PATCH] Avoid segfaulting in {start,finish}_decl
  - From: Richard Henderson
- Re: [PATCH] Avoid segfaulting in {start,finish}_decl
  - From: Jakub Jelinek

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