Dave Yeo wrote:> The nature of the error implies AVX2 support that is missing but I'm not > much up on assembly, > > Best to be safe so updated patch attached. > I've also opened a ticket, http://trac.netlabs.org/rpm/ticket/165#ticket > DaveI cannot find information what version of binutils supports AVX/AVX2/FMA instructions, but IIRC OS/2 doesn't support AVX instructions anyway, so it doesn't matter much.
On 01/18/16 01:46 PM, lvqcl wrote:> Dave Yeo wrote: > >> The nature of the error implies AVX2 support that is missing but I'm not >> much up on assembly, >> >> Best to be safe so updated patch attached. >> I've also opened a ticket, http://trac.netlabs.org/rpm/ticket/165#ticket >> Dave > > I cannot find information what version of binutils supports AVX/AVX2/FMA > instructions, but IIRC OS/2 doesn't support AVX instructions anyway, > so it doesn't matter much.Surprisingly, I've yet to have a report of an AVX related crash or trap (used in FFmpeg and projects based on it, Mozilla, probably others). As I understand it, support is a matter of saving the extended registers during a context switch and perhaps our kernel had some future proofing added towards the end. Dave
Dave Yeo wrote:>> I cannot find information what version of binutils supports AVX/AVX2/FMA >> instructions, but IIRC OS/2 doesn't support AVX instructions anyway, >> so it doesn't matter much. > > Surprisingly, I've yet to have a report of an AVX related crash or trap > (used in FFmpeg and projects based on it, Mozilla, probably others). > As I understand it, support is a matter of saving the extended registers > during a context switch and perhaps our kernel had some future proofing > added towards the end.WinXP/Vista also don't support AVX but ffmpeg doesn't crash there. IIRC, OS must explicitely enable AVX support, and an application must check whether the OS supports AVX or not.