https://sourceware.org/bugzilla/show_bug.cgi?id=25550
--- Comment #17 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Jan Beulich from comment #16) > (In reply to H.J. Lu from comment #14) > > (In reply to Jan Beulich from comment #13) > > > Well, that's what is described by my 2nd option, but it is (as explained) > > > specifically not sufficient to merely exclude all uses of MMX registers to > > > achieve this. > > > > It is no difference from > > > > if (i.has_regmmx > > || i.tm.base_opcode == 0xf77 /* emms */ > > || i.tm.base_opcode == 0xf0e /* femms */) > > x86_feature_2_used |= GNU_PROPERTY_X86_FEATURE_2_MMX; > > It is, for the case where no MMX register is used, but MMX state still gets > engaged (like CVTPI2PS with a memory operand). We need to handle these 2 like EMMS: cvtpi2ps, 2, 0xf2a, None, 2, CpuSSE, Modrm|IgnoreSize|No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|NoAVX, { Qword|Unspecified|BaseIndex|RegMMX, RegXMM } cvtpi2pd, 2, 0x660f2a, None, 2, CpuSSE2, Modrm|IgnoreSize|No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|NoAVX, { Qword|Unspecified|BaseIndex|RegMMX, RegXMM } -- You are receiving this mail because: You are on the CC list for the bug.