JuliaSIMD / CPUSummary.jl

MIT License
7 stars 4 forks source link

InitError when porting precompiled module #5

Closed tobiaslcmueller closed 2 years ago

tobiaslcmueller commented 2 years ago

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
chriselrod commented 2 years ago

Please check if the master branch fixes it: https://github.com/JuliaSIMD/CPUSummary.jl/commit/de28b206c5327a51a0fa4d7d415ffd4005ae74a1

tobiaslcmueller commented 2 years ago

Fixed for me on this version. Thank you for the prompt response!