- User Since
- May 9 2018, 10:30 AM (5 w, 4 d)
Wed, Jun 13
I don't know how to check LLVM -stats using lit.
Sizes matches the output of llvm-size, compile time and link time are also fine.
Updated input size, used malloc to allocate memory for the array.
polly + O3 and only O3 are taking the same time. It seems like before code reaches Polly, It is already heavily optimized at O3 and Polly cannot find any further optimization possible on it even though it is in its SCoP.
Mon, Jun 11
Thu, Jun 7
Tue, Jun 5
Sat, Jun 2
Fri, Jun 1
Fixed "backprop.h" showing as exec.
May 11 2018
But the fraction of noise will be more for shorter runtimes. A longer runtime will help us when we to see the performance improvement after applying optimization.
- I'd go for "MultiSource" benchmarks, even if they end up being a single source file; Producing multiple executables out of a single directory of source files is more complicated than it seems.
- Did you check the amount of time spent on initializing and printing the image compared to the main operation of the benchmark?
No, Do we need to submit the time values also when we add a new benchmark/kernel?
About 8% of total time that program takes was spent in the sobel_edge_detection function.