Re: LL(1) vs LALR(1) parsers

bridges@cs.arizona.edu (Patrick Bridges)
Fri, 1 Dec 1995 23:15:46 GMT

          From comp.compilers

Related articles
[13 earlier articles]
Re: LL(1) vs LALR(1) parsers ok@cs.rmit.edu.au (1995-11-29)
Re: LL(1) vs LALR(1) parsers mparks@oz.net (1995-11-29)
Re: LL(1) vs LALR(1) parsers jmccarty@spdmail.spd.dsccc.com (1995-11-29)
Re: LL(1) vs LALR(1) parsers pardo@cs.washington.edu (1995-11-29)
Re: LL(1) vs LALR(1) parsers CSPT@giraffe.ru.ac.za (Pat Terry) (1995-11-30)
Re: LL(1) vs LALR(1) parsers gvcormac@plg.uwaterloo.ca (Gord Cormack) (1995-12-01)
Re: LL(1) vs LALR(1) parsers bridges@cs.arizona.edu (1995-12-01)
Parse tables as code (WAS: LL(1) vs LALR(1) parsers) pardo@cs.washington.edu (1995-12-09)
Re: LL(1) vs LALR(1) parsers mparks@oz.net (1995-12-09)
Re: LL(1) vs LALR(1) parsers maatwerk@euronet.nl (1995-12-09)
Re: LL(1) vs LALR(1) parsers sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) (1995-12-09)
Re: LL(1) vs LALR(1) parsers mparks@oz.net (1995-12-12)
Re: LL(1) vs LALR(1) parsers solution@gate.net (1995-12-16)
[3 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: bridges@cs.arizona.edu (Patrick Bridges)
Keywords: parse, LALR, performance
Organization: The University of Arizona, Tucson, AZ
References: 95-11-138 95-11-195 95-11-230 95-11-242
Date: Fri, 1 Dec 1995 23:15:46 GMT

David Keppel writes:


>%A Thomas J. Pennello
>%T Very Fast LR Parsing
>%J Proceedings of the SIGPLAN 1986 Symposium on Compiler Construction;
>SIGPLAN Notices
>%V 21
>%N 7
>%D July 1986
>%P 145-151
>%X * Partial evaluation of the table interpreter with resepct to each
>element of the table (though not described as such).
> * On a VAX-like machine, 40,000 to 500,000 lines per minute. On an
>80286, 37,000 to 240,000 lines per minute.
> * FSM converted to assembly language, 2-4X increase in table size.


> ;-D on ( Parsetial Evaluation ) Pardo


Note that Penello's LR parser did not actually include *actions* or
error recovery... Someone I know actually implemented Penello's scheme
inside of Bison, and this sped up the generated parser on a cut-down C
(used in a local compiler class) grammar from 300% to 600% (on
pre-tokenized input). On the other hand, the generated parsers were
enormous since Penello's scheme encodes most of the parsing tables in
instruction state.
--
*** Patrick G. Bridges bridges@cs.arizona.edu ***
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.