3 Commits

Author	SHA1	Message	Date
jochen@chromium.org	56a486c322	Use full include paths everywhere ... - this avoids using relative include paths which are forbidden by the style guide - makes the code more readable since it's clear which header is meant - allows for starting to use checkdeps BUG=none R=jkummerow@chromium.org, danno@chromium.org LOG=n Review URL: https://codereview.chromium.org/304153016 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21625 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	2014-06-03 08:12:43 +00:00
marja@chromium.org	dccd57f1ec	Add parser-shell. ... parser-shell will help to see how much PreParsing gets slower when PreParser starts doing more checks (especially tracking variables and scopes). It will also show how much having preparse data (or cached data) speeds up the parsing. R=ulan@chromium.org BUG= Review URL: https://codereview.chromium.org/209353008 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20201 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	2014-03-24 14:43:41 +00:00
ulan@chromium.org	81761f9dc6	Add lexer-shell for running lexer benchmarks. ... R=jkummerow@chromium.org Review URL: https://chromiumcodereview.appspot.com/70263003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17692 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	2013-11-13 12:26:09 +00:00