-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still seeing the "WARNING: Wrapping Vararg
..." warnings with LoopVectorization v0.9.9 and VectorizationBase v0.14.3
#175
Comments
It's fixed in 0.9.9. I guess I should tag a new release. |
I'm still seeing this with Example log: (click to expand)
|
Vararg
..." warnings with LoopVectorization v0.9.8
and VectorizationBase v0.14.3
Vararg
..." warnings with LoopVectorization v0.9.9 and VectorizationBase v0.14.3
> jm --depwarn=error
julia> versioninfo()
Julia Version 1.7.0-DEV.122
Commit 676ccf4eaa (2020-12-18 19:53 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-11.0.0 (ORCJIT, tigerlake)
julia> using LoopVectorization
[ Info: Precompiling LoopVectorization [bdcacae8-1622-11e9-2a5c-532679323890]
julia> I cannot reproduce. |
Deleting my full compile cache, I see that there is at least on in ArrayInterface. |
Yeah I did |
Here's what I do to reproduce:
|
Oh I see what you mean - you're saying the occurences in LoopVectorization have been fixed, but there are still some left in ArrayInterface. |
Anyway, thanks @DilumAluthge for pointing it out! |
Originally mentioned in this comment and this comment.
Regarding the repeated
WARNING: Wrapping Vararg directly in UnionAll is deprecated (wrap the tuple instead)
warnings that only come up during precompilation - I'm still seeing those warnings.I'm on Julia master with
LoopVectorization v0.9.8
andVectorizationBase v0.14.3
(with AFAICT are the latest versions), and I see these warnings when I dorm -rf ~/.julia/compiled/
and then run the Gaius.jl test suite.The text was updated successfully, but these errors were encountered: