Add quickcheck targets for modes, builds and arches.

Add quickcheck targets for modes, builds and arches.

R=svenpanne@chromium.org

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

[Benedikt Meurer, 2014-03-05 09:13:56]

PTAL

[Sven Panne, 2014-03-05 09:32:33]

LGTM with a nit.

https://codereview.chromium.org/181013014/diff/1/Makefile
File Makefile (right):

https://codereview.chromium.org/181013014/diff/1/Makefile#newcode275
Makefile:275: mips mips.release mips.debug mips.optdebug:
I think we should rename these targets to "mipseb.foo" while we are here to make
it very explicit that we're talking about big-endian.

[Benedikt Meurer, 2014-03-05 11:31:08]

https://codereview.chromium.org/181013014/diff/1/Makefile
File Makefile (right):

https://codereview.chromium.org/181013014/diff/1/Makefile#newcode275
Makefile:275: mips mips.release mips.debug mips.optdebug:
On 2014/03/05 09:32:33, Sven Panne wrote:
> I think we should rename these targets to "mipseb.foo" while we are here to
make
> it very explicit that we're talking about big-endian.

Separate issue.

[Jakob Kummerow, 2014-03-05 12:48:52]

DBC.

https://codereview.chromium.org/181013014/diff/1/Makefile
File Makefile (right):

https://codereview.chromium.org/181013014/diff/1/Makefile#newcode275
Makefile:275: mips mips.release mips.debug mips.optdebug:
On 2014/03/05 09:32:33, Sven Panne wrote:
> I think we should rename these targets to "mipseb.foo" while we are here to
make
> it very explicit that we're talking about big-endian.

I think these targets should remain exactly as they are -- look at the line
below, all they do is throw an error message.
If and when we add a big-endian MIPS port, we can call it mipseb for clarity,
but even then we should keep these target definitions, with a slightly updated
message like "'mips' is ambiguous, please build either 'mipsel' or 'mipseb'
targets".

[Benedikt Meurer, 2014-03-06 10:05:38]

Committed patchset #2 manually as r19686 (tree was closed).

[Jakob Kummerow, 2014-03-12 09:53:28]

More DBC:

What exactly is the point of these targets? AFAICS "make foo.quickcheck" is just
short for "make foo.check TESTFLAGS=--quickcheck". Notably this is *not* the
same as the "foo" part of "make quickcheck", as foo.quickcheck builds and runs
full debug mode rather than optdebug.

So all this does compared to the usual foo.check targets is skip long-running
tests. IMHO this difference is not worth a separate target definition, the
similarity to "make quickcheck" is confusing, and this CL should be reverted.