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

pardo@cs.washington.edu (David Keppel)
Wed, 29 Nov 1995 19:08:39 GMT

          From comp.compilers

Related articles
[10 earlier articles]
Re: LL(1) vs LALR(1) parsers will@ccs.neu.edu (1995-11-28)
Re: LL(1) vs LALR(1) parsers ddean@dynastar.cs.princeton.edu (1995-11-28)
Re: LL(1) vs LALR(1) parsers napi@ms.mimos.my (1995-11-28)
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)
[6 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: pardo@cs.washington.edu (David Keppel)
Keywords: parse, LALR, LL(1)
Organization: Computer Science & Engineering, U. of Washington, Seattle
References: 95-11-138 95-11-195 95-11-230
Date: Wed, 29 Nov 1995 19:08:39 GMT

>>[Why recursive descent parsing?]


ddean@cs.princeton.edu (Drew Dean) writes:
>[Because it's faster.]


%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


--


Post a followup to this message

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