You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to JuliaSIMD/VectorizationBase.jl#57, I experience the following InitError, when porting the precompiled module between different machines. Seems to be the same bug, but now triggered in a different subpackage of LoopVectorization.
ERROR: InitError: TypeError: non-boolean (Nothing) used in boolean context
Stacktrace:
[1] _define_cache(N::Int64, c::NamedTuple{(:size, :linesize, :associativity, :type, :inclusive), Tuple{Int64, Int64, Nothing, Nothing, Nothing}})
@ CPUSummary ~/.julia/packages/CPUSummary/ZAemo/src/topology.jl:221
[2] redefine_cache(N::Int64)
@ CPUSummary ~/.julia/packages/CPUSummary/ZAemo/src/topology.jl:246
[3] foreach
@ ./abstractarray.jl:2694 [inlined]
[4] __init__()
@ CPUSummary ~/.julia/packages/CPUSummary/ZAemo/src/CPUSummary.jl:18
[5] _include_from_serialized(path::String, depmods::Vector{Any})
@ Base ./loading.jl:768
[6] _require_search_from_serialized(pkg::Base.PkgId, sourcepath::String)
@ Base ./loading.jl:854
[7] _tryrequire_from_serialized(modkey::Base.PkgId, build_id::UInt64, modpath::String)
@ Base ./loading.jl:783
[8] _require_search_from_serialized(pkg::Base.PkgId, sourcepath::String)
@ Base ./loading.jl:843
[9] _tryrequire_from_serialized(modkey::Base.PkgId, build_id::UInt64, modpath::String)
@ Base ./loading.jl:783
[10] _require_search_from_serialized(pkg::Base.PkgId, sourcepath::String)
@ Base ./loading.jl:843
[11] _require(pkg::Base.PkgId)
@ Base ./loading.jl:1097
[12] require(uuidkey::Base.PkgId)
@ Base ./loading.jl:1013
[13] require(into::Module, mod::Symbol)
@ Base ./loading.jl:997
during initialization of module CPUSummary
The text was updated successfully, but these errors were encountered:
Similar to JuliaSIMD/VectorizationBase.jl#57, I experience the following InitError, when porting the precompiled module between different machines. Seems to be the same bug, but now triggered in a different subpackage of LoopVectorization.
The text was updated successfully, but these errors were encountered: