Separate LoopVectorization.vsum from VectorizationBase.vsum#516
Separate LoopVectorization.vsum from VectorizationBase.vsum#516brenhinkeller wants to merge 2 commits intoJuliaSIMD:mainfrom brenhinkeller:main
LoopVectorization.vsum from VectorizationBase.vsum#516Conversation
|
Thanks for addressing this/taking over from #515. |
|
Oh oops I hadn’t noticed #515! Looks like this is still breaking something, but I don't think I understand why.. |
Some failures are because LV uses VectorizationBase.vsum, without saying VectorizationBase.vsum. |
|
That would make sense but I can't find any other usages of |
E.g. LoopVectorization.jl/src/modeling/costs.jl Lines 599 to 601 in d2f749d LoopVectorization.jl/src/modeling/operations.jl Lines 564 to 565 in d2f749d LV doesn't call the code, it generates expressions with calls. |
|
Ooh, so is it as simple as replacing that with |
Note that |
Seems like it might be better to have
LoopVectorization.vsum != VectorizationBase.vsumesp. if we might want to extend the former (but not the latter) in other packages. I think this isn't technically breaking and hopefully it doesn't break anything if I did it right, but will see how tests look