Open ufechner7 opened 3 years ago
The constants in the generated code are randomized with a seed depending the current time and date to make caching impossible and comparison fairer so I see no reason to not closed this issue. See https://github.com/nordlow/compiler-benchmark#compiler-object-caches for details.
Currently I'm assuming that compilation is much slower than the run-time and bake these into the same metric for Julia. Would it be possible to alleviate this by writing a Julia wrapper script that first benchmarks the compilation and then the running of the generated main.jl
enabling the Run-Time column to be populated by a real metric?
It should be possible to use PackageCompiler.jl to compile the code, and then run it separately.
If I execute:
I get the following result:
So for the Run Time we get the result N/A.
If I run Julia from the command line and execute:
So the the execution time is zero, because the result is already calculated during compile time using constant propagation.
This means in the result table you should also report zero run time.
Or modify the test code so that full constant propagation is not possible.