abadams on master
Add unsharp app, with fresh man… Delete defunct unsharp test Add and reschedule harris corne… and 14 more (compare)
abadams on avoid_type_punning_when_making_shapes
Avoid type punning in the gener… (compare)
abadams on apps_from_autoscheduler
Don't rely on weak linkage (compare)
steven-johnson on srj-msan-stringify
bin/Demosaic.o', needed bybin/process'. Stop.
Hi All, i was looking at issue 2317 (halide/Halide#2317) where input.dim(0).set_min(0) was resulting in slower code on CPU. Further digging into code and some experiment showed that slowness is only due to input.dim(0).set_min(0) and not due to input.dim(1).set_min(0).
In the codegen, i see some checks and asserts for "halide_buffer_is_bounds_query" and these are inserted on CPU side always. Even if the schedule is offloaded to Hexagon, the asserts are always inserted in CPU code. Hence the slowness is always observed on CPU schedule, but not on Hexagon.
Q - For schedules offloaded to Hexagon, even if the asserts are on CPU side, why isn't slowness observed? I assume we are measuring time which involves the CPU to Hexagon and back offload time too. Any idea?