Leszek Swirski d8c9ae5295 [compiler] Fix double error reporting for parser errors ... Remove error reporting from parsing::Parse*, since in most cases we didn't actually want them (clear errors afterward), and there was an issue where Compiler::Compile would try to report errors already reported in ParseAny, which ended up triggering unreachable code. As a drive-by, move some one-off parse exception handling in test-parsing into a CHECKED_PARSE_PROGRAM macro which replaces all the "necessarily positive" calls to parsing::ParseProgram. Bug: chromium:1091656 Change-Id: I4d463ec363312aea36ab92f1322cf66a416b9888 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2237134 Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#68281}		2020-06-10 08:36:41 +00:00
..
test-parse-decision.cc	Move utility code to src/utils	2019-05-23 14:13:34 +00:00
test-preparser.cc	[compiler] Fix double error reporting for parser errors	2020-06-10 08:36:41 +00:00
test-scanner-streams.cc	Fix compilation error with devtoolset-8	2020-04-21 12:27:48 +00:00
test-scanner.cc	Reland^5 "[parser] Introduce UnoptimizedCompileFlags"	2020-04-22 11:35:35 +00:00