Steffen Schultze

Yes, this appears to fix it. The features are now detected correctly also for me and the cache file gets properly rejected.

```julia julia> Base.parse_image_targets(Base.parse_cache_header("/home/sschult/.julia/compiled/v1.11/JLD2/O1EyT_NIQbS.ji")[7]) 1-element Vector{Base.ImageTarget}: cascadelake; flags=0; features_en=(sse3, pclmul, ssse3, fma, cx16, sse4.1, sse4.2, movbe, popcnt, aes, xsave, avx, f16c, fsgsbase, bmi, avx2, bmi2, adx, clflushopt, clwb, sahf, lzcnt, prfchw,...

That's exactly what I did. In fact, the same .so file is reported on both machines, and the output is exactly the same.

In 1.10, I get ```julia julia> Base.parse_image_targets(Base.parse_cache_header("/home/sschult/.julia/compiled/v1.10/JLD2/O1EyT_NQjXZ.ji")[7]) 1-element Vector{Base.ImageTarget}: cascadelake; flags=0; features_en=(sse3, pclmul, ssse3, fma, cx16, sse4.1, sse4.2, movbe, popcnt, aes, xsave, avx, f16c, fsgsbase, bmi, avx2, bmi2, avx512f, avx512dq,...

After some further testing, I found that the issue appears first in 1.11.0-rc4, with rc3 unaffected. Also, in rc3, `Base.current_image_target()` correctly contains the avx512 features, whereas in rc4 it does...

From checking the automatic builds 50c1ea848579ddc99e3c3633b85669988c2c89f2 appears to be the first commit affected.