Steven Johnson
Steven Johnson
I think the issue here is that the test for the li2018 autoscheduler is generating vectorized code, but the RISCV backend needs explicit vector width support in its target string....
Sorry, I don't know.
FWIW, this fails to build properly on my macOS laptop; it segfaults (!) trying to build the autoschedulers. (`Apple clang version 15.0.0 (clang-1500.1.0.2.5)`)
Adding @rootjalex as reviewer specifically for XtensaOptimize, due to its similarity to HexagonOptimize
@dragly I can't tell you how happy I am that someone is making good use of the Python bindings! (They never got the uptake I was hoping for inside Google.)...
I'm not aware that any of the Halide core contributors have ever looked into making this work, so, yeah, it's probably nt working. We'd be happy for someone else to...
> some tweaks in halide's python bindings code will really help. At the moment we don't have any resources available to work on this, but we'd be very happy to...
My grab-bag of thoughts: - Figure out useful guidance for practical Halide-on-GPU usage and update the code/examples/docs accordingly. For instance: by far, the most questions about GPU usage that I...
Possible, yes... plausible, eh, I dunno. 15 minutes is a *long* time to run a Generator. Even in debug mode that's a long time.
Yeah -- IMHO the timeout should be in the build system, not the Generator