Re: compile bug in HEAD? - Mailing list pgsql-hackers

From nconway@klamath.dyndns.org (Neil Conway)
Subject Re: compile bug in HEAD?
Date
Msg-id 20020331011113.GF27863@klamath.dyndns.org
Whole thread Raw
In response to Re: compile bug in HEAD?  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: compile bug in HEAD?  (Peter Eisentraut <peter_e@gmx.net>)
Re: compile bug in HEAD?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Wed, Mar 27, 2002 at 07:56:15PM -0500, Peter Eisentraut wrote:
> Neil Conway writes:
> 
> > I'm curious; why is this "not the right fix"? According to the manpage:
> >
> > -l    turns  on  maximum compatibility with the original
> >     AT&T lex implementation. Note that this does not
> >     mean full compatibility.  Use of this option
> >     costs a  considerable  amount  of performance...
> 
> The manpage also lists the specific incompatibilities.  I think we should
> not be affected by them, but someone better check before removing the -l.

AFAICT current sources don't actually use "-l" anywhere.

However, it does appear that we can tweak flex for more performance
(usually at the expense of a larger generated parser). In particular, it
looks like we could use "-Cf" or "-CF". Is this a good idea?

While we're on the subject of minor optimizations, is there a reason why
we execute gcc with "-O2" rather than "-O3" during compilation?

Cheers,

Neil

-- 
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: rules and default values
Next
From: Peter Eisentraut
Date:
Subject: Re: compile bug in HEAD?