Allow easy repetitions of benchmarks
Currently if I wan't to rerun a benchmark but with different parameters (iterations and other args to be passed to the benchmark program) i have to edit the '.yml' file and rerun mubench. This is problematic for two reasons, one every execution of mubench recompile (which takes a while) and frequent editing of the .yml is tedious and time consuming.
As such I have two suggestions:
- Make mubench use some kind of (intelligent?) mechanism to determine whether to recompile (e.g. like make use), but have an option to force recompilation.
- Allow parsing extra arguments to mubench that get forwarded to the program (maybe have a sentinel value like '-' that will force it to read the corresponding parameter from the '.yml' file
As an example you could then do:
python3 mubench local example/test_except.yml -r - - 200
Where the '-r' indicates to forcefully recompile, and the arguments passed to the program are then a b 200
where a and b are the arguments that would have been passed if you didn't specify any (so b is read from the .yml file and 'a' is some kind of clock id??)