I agree to Sven's suggestions. I can set up some builders on the waterfall
to
run a special config, once it is ready (just give me a note).
The "arm" builder that runs on real hardware is still quite fast, so I
suggest
we split it into two, one with and one without the flag (and optionally one
being a release and the other a debug builder).
Then I just "randomly" select one builder of each other platform to run with
that flag on.
Alternative: When passing in via --extra-flags=--optimize-for-size, every
test
variant will have the optimize-for-size flag set. Another option would be to
extend the run-tests script with a new optimize-for-size parameter that,
only
when set, adds a variant with just optimize-for-size to the other three
variants. Then we would have +33% on a few selected builders, while also
keeping
the old test configurations.
What way to go depends on if you want the cross product of that flag with
the
other variants or not.
https://codereview.chromium.org/49633004/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
