steven-johnson on init-from-context
Minor metadata-related cleanups… Expand the x86 SIMD variants te… Fix Param<T>::set_estimate for … and 6 more (compare)
steven-johnson on typo2
steven-johnson on main
Fix annoying typo in Func.h (#6… (compare)
backports/N.xfor staging changes to
release/N.x. When it's ready, I open a PR with
release/N.xas the target branch. There is CI set up for this scenario. Be sure to include a commit that bumps the version to
release/N.xis (or ought to be) protected (like
master), so you can't push to it
release/N.x. I think the cherry-picking history is valuable (as are any separate/additional patches necessary to correctly backport) as is keeping the version number bump separate.
share/doc/Halidefolder (at least on Linux), along with the other READMEs.
Loop over output.s0.x has extent output.extent.0. Can only vectorize loops over a constant extent > 1. Let's say we're dealing with floats and SSE, I don't get why the loop over
xcan't simply loop over 1/4 of the extent and process 4 float values at the time (let's ignore the case where extent is not divisible by 4). Do I need to split
xinto constant size chunks in order to get vectorization working?
$ objdump -t build/host/ResizeNearestNeighbor.a | grep halide_ 00000000 l df *ABS* 00000000 halide_buffer_t.cpp 00000000 *UND* 00000000 halide_error 00000000 *UND* 00000000 halide_msan_annotate_memory_is_initialized 00000000 w F .text.halide_qurt_hvx_lock 000000b0 halide_qurt_hvx_lock 00000000 w F .text.halide_qurt_hvx_unlock 000000ac halide_qurt_hvx_unlock 00000000 w F .text.halide_qurt_hvx_unlock_as_destructor 00000008 halide_qurt_hvx_unl ock_as_destructor 00000000 *UND* 00000000 halide_string_to_string 00000000 w F .text.halide_vtcm_free 00000008 halide_vtcm_free 00000000 w F .text.halide_vtcm_malloc 0000000c halide_vtcm_malloc