Ivy Bridge CPUs crashing on AVX2.0 code paths in macOS 13.3

[khronokernel]

Reported by MacPro6,1 and iMac13,2, CoreGraphics's resample_horizontal_f16c() invokes the AVX2.0 OpCode vpbroadcastw. Currently under investigation regarding whether Apple bug or something that can be resolved locally.

• Crash Log

[ASentientBot]

notes from when ghoover101 on discord encountered this

___CGGetHardwareVectorCapabilities_block_invoke checks hw.optional.f16c hw.optional.avx2_0 hw.optional.avx512bw

given f16c in the crashing function name, possible explanation is an apple logic bug assuming f16c implies avx2?

extremely dumb test hex-editing hw.optional.f16c (present on Ivy) to hw.optional.bmi1 (not present) resolved the issue for that user. needs to be re-tested.

questions - reverse CG and find where it picks these codepaths.
is the use of vpbroadcastw here the avx2 or avx512 version?
can this be solved by routing sysctl in kernelspace (Flagers suggestion) or FeatureUnlock patching similar to my hex edit (dumb approach)?
does this occur on all machines with f16c but no avx2? note - doesn't on Zoe which lacks both

another report

[khronokernel]

c0825ed