Re: Bison =?UTF-8?B?ZGV0ZXJtaW5pc+KAi3RpYyBMQUxSKDEpIHBhcnNlciBm?= =?UTF-8?B?b3IgSmF2YS9DKysgKGtpbmQgb2YgY29tcGxleCBsYW5nYXVnZSkgd2l0aG91dCA=?= =?UTF-8?B?J2xleGFyIGhhY2snIHN1cHBvcnQ=?=

Hans-Peter Diettrich <DrDiettrich1@aol.com> writes:
>> [Get it working in bison, then in the unlikely event that's not fast
>> enough, profile your compiler to see where it's spending its time and
>> fix what needs to be fixed. Although in theory GLR can be very slow,
>> in practice the ambiguities are generally resolved within a few tokens
>> and the performance is fine. compilers always spend way more time in
>> the lexer than the parser anyway. Writing RD parsers by hand can be
>> fun, but you never know what language it actually parses. -John]
>
>There exist parser generators for several models. I also doubt that -
>except in misdesigned C-ish languages - a compiler spends significant
>time in the lexer. This may be true for dummy parsers, which do
>nothing but syntax checks, but not for compilers with code generation,
>optimization and more.


Code generation and optimization do not change the relation between
the time spent in scanning and in parsing. Moreover, if the compiler
spends most of the time in code generation, optimization and/or
"more", there is even less reason to worry about parsing speed.


- anton
--
M. Anton Ertl
anton@mips.complang.tuwien.ac.at
http://www.complang.tuwien.ac.at/anton/

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