Update tests to use the new compilation API.

Update tests to use the new compilation API + related fixes.

Esp. get rid of PreCompile in tests, as it's going to be removed.

Notes:
- The new compilation API doesn't have a separate precompilation phase, so there
is no separate way to check for errors except checking the compilation
errors. Removed some tests which don't make sense any more.
- test-api/Regress31661 didn't make sense as a regression test even before the
compilation API changes, because Blink doesn't precompile this short scripts. So
detecting this kind of errors (see crbug.com/31661 for more information) cannot rely
on precompilation errors.
- test-parsing/PreParserStrictOctal has nothing to do with PreParser, and the comment
about "forcing preparsing" was just wrong.
- test-api/PreCompile was supposed to test that "pre-compilation (aka
preparsing) can be called without initializing the whole VM"; that's no longer
true, since there's no separate precompilation step in the new compile
API. There are other tests (test-parsing/DontRegressPreParserDataSizes) which
ensure that we produce cached data.
- Updated tests which test preparsing to use PreParser directly (not via the
 preparsing API).
- In the new compilation API, the user doesn't need to deal with ScriptData
ever. It's only used internally, and needed in tests that test internal aspects
(e.g., modify the cached data before passing it back).
- Some tests which used to test preparse + parse now test first time parse +
  second time parse, and had to be modified to ensure we don't hit the
  compilation cache.



BUG=
R=ulan@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=20511

[marja, 2014-04-04 11:41:25]

ulan, ptal

[ulan, 2014-04-04 12:10:59]

lgtm

https://codereview.chromium.org/225743002/diff/40001/src/parser.h
File src/parser.h (right):

https://codereview.chromium.org/225743002/diff/40001/src/parser.h#newcode120
src/parser.h:120: if (functions_size < 0) return 0;
Shouldn't these checks be ASSERTs instead?
What does it mean if the size is negative or not a multiple of the entry size?

[marja, 2014-04-04 12:13:17]

thanks for review!

https://codereview.chromium.org/225743002/diff/40001/src/parser.h
File src/parser.h (right):

https://codereview.chromium.org/225743002/diff/40001/src/parser.h#newcode120
src/parser.h:120: if (functions_size < 0) return 0;
On 2014/04/04 12:10:59, ulan wrote:
> Shouldn't these checks be ASSERTs instead?
> What does it mean if the size is negative or not a multiple of the entry size?

It's just invalid data then. The length field is tells how many ints we have
which describe the function data, and each function takes FunctionEntry::kSize
ints. So if the length is not non-negative multiple of FunctionEntry::kSize, the
data is wrong.

[marja, 2014-04-04 12:36:30]

Committed patchset #4 manually as r20511 (presubmit successful).