Change run_vm_tests to take the VM arguments before the test name so

Change run_vm_tests to take the VM arguments before the test name so
it acts more like the standalone VM. That way the test scripts can
uniformly pass extra arguments to the cctest runner and to the VM
itself.

The use case for this is that it is nice to be able to add extra
vm flags to all tests using the --special-commands flag for the
test runner:

./tools/test.py --special-commands='time @ --vm-flag'

This will turn cc tests into:

time run_vm_tests --vm-flag Selector

and VM tests into:

time dart --vm-flag my_test.dart

R=ricow@google.com,asiva@google.com
BUG=

Committed: https://code.google.com/p/dart/source/detail?r=13067

[ricow1, 2012-10-01 13:50:28]

LGTM

http://codereview.chromium.org/11018014/diff/1/runtime/bin/run_vm_tests.cc
File runtime/bin/run_vm_tests.cc (right):

http://codereview.chromium.org/11018014/diff/1/runtime/bin/run_vm_tests.cc#ne...
runtime/bin/run_vm_tests.cc:88: fprintf(stderr, "run_vm_tests  <test name>
[vm-flags ...]\n");
we should update these to reflect the new structure

http://codereview.chromium.org/11018014/diff/1/runtime/bin/run_vm_tests.cc#ne...
runtime/bin/run_vm_tests.cc:103: } else if (argc == 2) {
I think we may need to update the functionality in here as well. Additionally,
if we have exactly one vm flag and the testname we will hit the else clause in
the button of this clause and _not_ get the flag passed on the the vm (i.e., we
ignore it)

[Mads Ager (google), 2012-10-01 14:03:38]

http://codereview.chromium.org/11018014/diff/1/runtime/bin/run_vm_tests.cc
File runtime/bin/run_vm_tests.cc (right):

http://codereview.chromium.org/11018014/diff/1/runtime/bin/run_vm_tests.cc#ne...
runtime/bin/run_vm_tests.cc:88: fprintf(stderr, "run_vm_tests  <test name>
[vm-flags ...]\n");
On 2012/10/01 13:50:28, ricow1 wrote:
> we should update these to reflect the new structure

Done.

http://codereview.chromium.org/11018014/diff/1/runtime/bin/run_vm_tests.cc#ne...
runtime/bin/run_vm_tests.cc:103: } else if (argc == 2) {
On 2012/10/01 13:50:28, ricow1 wrote:
> I think we may need to update the functionality in here as well. Additionally,
> if we have exactly one vm flag and the testname we will hit the else clause in
> the button of this clause and _not_ get the flag passed on the the vm (i.e.,
we
> ignore it)

This is the argc == 2 case where argv[0] is the executable and there is only one
more argument argv[1] which is either one of these flags or a run_filter. So no
update is needed here.