halo-project/halo

Tuning Section Selection

Closed this issue · 0 comments

kavon commented

With the overhead elimination stuff, fixed_workload's profiling data suggests to the TS selector that driverFn is a better tuning root than workFn, even though driverFn is only called once at the start of the program. The ancestor hotness check needs to look two ancestors back, not one, to see if we can expand the TS region.

This would solve the issue seen in: c583137