[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: push parser implemenation

From: Bob Rossi
Subject: Re: push parser implemenation
Date: Wed, 19 Apr 2006 22:25:14 -0400
User-agent: Mutt/1.5.9i

On Wed, Apr 19, 2006 at 09:26:50PM -0400, Joel E. Denny wrote:
> On Mon, 17 Apr 2006, Bob Rossi wrote:
> > Hi everyone, I hope I can get some suggestions soon. I don't want this
> > to be forgotten about. 
> > 
> > Either we can make the push parser a separate file
> There are 4 skeletons now.  Push parser mode could be desirable for any of 
> them.  Coding the push parser in separate skeletons could mean a total of 
> 8 skeletons and a lot of redundant code.  This doesn't seem like the right 
> way to go.

I agree. Plus, the changes are not large.

> >, we can allow the user to loose the 10% speed performance
> I'm not concerned with this performance loss much for my current usage, 
> but I imagine this is not acceptable to many Bison users.

I have a patch that I'll post here shortly. Still trying to generate a
parser that works. It should increase the performance and get yacc mode
within 1% of it's original speed.

> >, I can attempt to do the above
> > suggestion, or
> > 
> > I can see what happens if I declare the struct globally, and when in
> > push-yacc and pure-yacc mode, declare variables on the stack with the
> > same name as the struct's fields. This may improve the speed.
> I don't have time to study these two alternatives and form a thoughtful 
> opinion.  It seems that others don't at the moment either.  Maybe you 
> could try one or both and report your findings.

I appreciate the honest suggestion. After I post the next patch, maybe I
could get some feedback. It is a smaller patch.

Bob Rossi

reply via email to

[Prev in Thread] Current Thread [Next in Thread]