Conversation
This was supposed to be removed in Halide 17 (oops), removing for Halide 18
shoaibkamil
left a comment
There was a problem hiding this comment.
LGTM, thanks for doing this!
@TH3CHARLie Do we need to bump the serialization version? I'm not sure what our approach has been when deprecating features (maybe this is the first time since serialization was added).
IMHO we should probably bump the version for every Halide release, regardless |
I think anything that changes the serialization definition needs to bump the serialization version, on the minor number(i.e. 0.1.0 -> 0.1.1). And second to Steven's comment, we should bump the serialization version number on every major release. |
|
|
One thing I found about this PR is that, the serialization version numbers help users to find out they are deserializing from an old binary pipeline. But on the other hand, if you are using an old Halide build with a updated binary pipeline, the code may crash before we start to check the version numbers (because of a format change in this PR in particular): Halide/src/Deserialization.cpp Line 1405 in 9a740b5 |
* Remove OpenGLCompute This was supposed to be removed in Halide 17 (oops), removing for Halide 18 * Update dynamic_allocation_in_gpu_kernel.cpp * Update dynamic_allocation_in_gpu_kernel.cpp * Update halide_ir.fbs
This was supposed to be removed in Halide 17 (oops), removing for Halide 18