v8/test/unittests/torque
Tobias Tebbi ec2c299c42 [torque] check runtime function signatures properly
The missing check that runtime function parameters have to be tagged
lead to a bug: https://chromium-review.googlesource.com/c/v8/v8/+/1604071

drive-by-fix: Remove obsolete verbose mode. It hasn't been maintained
since the very early Torque versions, and the remaining printf's are
rather useless.

Bug: v8:7793
Change-Id: I59adf4c6c5d92a8838cdc638afb2ab7a41550b55
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1609910
Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#61483}
2019-05-14 13:35:32 +00:00
..
earley-parser-unittest.cc [torque] add unittest for Earley parser 2018-07-24 14:01:33 +00:00
ls-json-unittest.cc Reland^3 "[torque] Throw exception instead of aborting if something goes wrong" 2019-04-16 10:41:20 +00:00
ls-message-unittest.cc [torque-ls] Move GlobalContext into LangServerData after compilation 2019-05-14 05:43:06 +00:00
ls-server-data-unittest.cc [torque] check runtime function signatures properly 2019-05-14 13:35:32 +00:00
torque-unittest.cc [torque] check runtime function signatures properly 2019-05-14 13:35:32 +00:00
torque-utils-unittest.cc [torque-ls] fix Windows file paths 2019-04-24 08:17:07 +00:00