Closed tkalbitz closed 10 years ago
Hey Tobias,
Have a look at https://github.com/kid0m4n/rays/commit/eb78a3e6b806a667787f1247fb97ad1029188e8e
@t-mat and I were both talking about hardcoding "render.ppm" is a smell which will probably haunt us in near future. Hence, I really like the idea of small wrapper shell scripts which have the responsibility of running their respective benchmark by invoking the command in an appropriate manner.
This will not only allow us to capture details like "-XX:+AggressiveOpts" (as in the example you showed above), it will also allow us to leverage the best each platform has to offer (command line parsing, for eg.)
To that effect, I have implemented a bunch of changes to the Go version. Summary:
I know these changes are massive and will take time to replicate across all programs (and now we already have 5) but the earlier to answer some of these issues, the better off we will be
What do you reckon?
I am merging this in... it is a small change to get the desired state from here
This pull request updates the command line options and the output file to mimic the Go version. Also you can have more than one render run in an program invocation
Here is an example: