Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

parser+lexer run-time optimizations: strip kernel features which are unused #341

Open
GerHobbelt opened this issue Jan 31, 2017 · 0 comments
Open

parser+lexer run-time optimizations: strip kernel features which are unused #341

GerHobbelt opened this issue Jan 31, 2017 · 0 comments

Comments

@GerHobbelt
Copy link
Contributor

Reduce lexer run-time costs.

See also work done in #338 for the parser; now that work should continue into the lexer to achieve maximum 'parse' speeds.
@GerHobbelt GerHobbelt mentioned this issue Jan 31, 2017
Open
GerHobbelt added a commit to GerHobbelt/jison that referenced this issue Jan 31, 2017
@GerHobbelt
First bit of work for zaach#341: lexer run-time optimizations. For th…
22b521a 
…at to deliver, the lexer *generator* will need information about which features are used, e.g. extended error handling, location tracking (with or without `yylloc.range` range tracking), etc.
GerHobbelt added a commit to GerHobbelt/jison that referenced this issue Feb 1, 2017
@GerHobbelt
Strip out a then-invalid comment when --no-default-action is set fo…
384ee8a 
…r the given grammar: the kernel code should not carry blatantly incorrect comments either after kernel stripping! Sideways related to zaach#341.
GerHobbelt added a commit to GerHobbelt/jison that referenced this issue Feb 1, 2017
@GerHobbelt
Parser speed optimization zaach#341: when both --no-try-catch and `…
15747fc 
…--no-default-action` are specified, all safeties are moved, including protection in the kernel against incorrect use of `$$`/`$0` in grammar rule action code blocks. Example examples/test-unused-rules-reporting.jison is augmented to showcase the (**technically correct but functionally buggy!!!) behaviour.
GerHobbelt added a commit to GerHobbelt/jison-lex that referenced this issue Apr 8, 2017
@GerHobbelt
working on zaach#20 / zaach/jison#341: pass parser analysis info bits…
e1f3d87 
… to the lexer compiler using better names, so they are confused once in there.
GerHobbelt added a commit to GerHobbelt/jison-lex that referenced this issue Apr 8, 2017
@GerHobbelt
working on zaach#20 / zaach/jison#341: collecting the first few stati…
34c8223 
…stics of the generated lexer to be used in the code optimizer.
GerHobbelt added a commit to GerHobbelt/jison that referenced this issue Apr 8, 2017
@GerHobbelt
working on zaach/jison-lex#20 / zaach#341: pass parser analysis info …
1142438 
…bits to the lexer compiler using better names, so they are confused once in there.
GerHobbelt added a commit to GerHobbelt/jison-lex that referenced this issue Jun 25, 2017
@GerHobbelt
working on zaach/jison#341: extending the lexer analysis report in an…
acc6239 
…ticipation of what will be coming next: lexer code analysis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GerHobbelt