Lecture 24: High Performance Image Processing & Halide (77)
CptTeddy
Truly amazing. The readability of Halide while maintaining such high performance is respectable, and I really like this idea of modulization of algorithm and defining its schedules to make the code much less prune to calculation mistakes.
ryanpmeyer
Is halide specialized for certain hardware? For instance would the code on the left work on a single core CPU (with the right compiler)? If so it could be a much better alternative to writing code like on the right which can only be compiled and run on machines with Intel SSE instruction compatibility.
glinia
Halide reminds me in some ways of declarative programming: you declare what you want the data to look like, and then you let the scheduler decide how to make it happen. I suppose it's different if you explicitly declare a schedule, although it still retains the advantage of the separation of algorithm and schedule.
Truly amazing. The readability of Halide while maintaining such high performance is respectable, and I really like this idea of modulization of algorithm and defining its schedules to make the code much less prune to calculation mistakes.
Is halide specialized for certain hardware? For instance would the code on the left work on a single core CPU (with the right compiler)? If so it could be a much better alternative to writing code like on the right which can only be compiled and run on machines with Intel SSE instruction compatibility.
Halide reminds me in some ways of declarative programming: you declare what you want the data to look like, and then you let the scheduler decide how to make it happen. I suppose it's different if you explicitly declare a schedule, although it still retains the advantage of the separation of algorithm and schedule.