Displaying 3 results from an estimated 3 matches for "wall_time".
2015 Aug 19
3
RFC: PGO Late instrumentation for LLVM
...re are the average running time of 5 runs in
seconds.
*(1) Performance b/w late instrumentation v.s. not instrumenting single BB
functions*
We first compare various instrumentation performance.
----------------------------------------------------------------------------
Config wall_time_for_instr ratio_vs_base
profile_size
(1) base O2 80.386 100.0% --
(2) FE-based Instr 201.658 250.8% 65238880
(3) late Instr 103.662 129.0% 14860144
(4) (3) + w/o pre-inline 199.924...
2015 Sep 01
3
RFC: PGO Late instrumentation for LLVM
...n
> seconds.
>
> *(1) Performance b/w late instrumentation v.s. not instrumenting single BB
> functions*
>
> We first compare various instrumentation performance.
>
> ----------------------------------------------------------------------------
> Config wall_time_for_instr ratio_vs_base
> profile_size
> (1) base O2 80.386 100.0% --
> (2) FE-based Instr 201.658 250.8% 65238880
> (3) late Instr 103.662 129.0% 14860144
> (4) (3) + w/o...
2015 Aug 11
4
RFC: PGO Late instrumentation for LLVM
One aspect of this that I have not seen discussed is that middle-end
instrumentation enables PGO optimizations to front-ends other than Clang.
While I agree that FE instrumentation could be improved, it still requires
every FE to implement essentially the same common functionality. Having
PGO instrumentation generated in the middle-end, allows us every FE to
automatically take advantage of PGO.