This is the mail archive of the gcc@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: gcc compile-time performance

From: Akim Demaille <akim at epita dot fr>
To: Paul Koning <pkoning at equallogic dot com>
Cc: haberg at matematik dot su dot se, gcc at gcc dot gnu dot org, help-bison at gnu dot org
Date: 20 May 2002 20:18:23 +0200
Subject: Re: gcc compile-time performance
References: <20020520131209.B4F56F28CC@nile.gnat.com><v03110701b90ec49be4e5@[195.100.226.139]><15593.10867.946000.77135@gargle.gargle.HOWL>

>>>>> "Paul" == Paul Koning <pkoning@equallogic.com> writes:

Paul> Excerpt of message (sent 20 May 2002) by Hans Aberg:
>> As noted by Paul Hilfinger in the Bug Bison list, widespread access
>> to interactive computing makes it more prudent with a "compile to
>> the first syntax error, fix, and repeat" approach.

Paul> That makes no sense to me at all.  If I could only fix one typo
Paul> at a time, progress would be quite a bit slower.

I think Hans somewhat distorted Paul Hilfinger's statements.  Paul
also did mention the poor quality of today's error-recovery/correction
schemes as compared to what the 80's had brought.

No one here claims Bison's perfect wrt this!

Follow-Ups:
- Re: gcc compile-time performance
  - From: Hans Aberg

References:
- Re: gcc compile-time performance
  - From: Robert Dewar
- Re: gcc compile-time performance
  - From: Hans Aberg
- Re: gcc compile-time performance
  - From: Paul Koning

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