https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99234
--- Comment #18 from Liu Hao <lh_mouse at 126 dot com> --- (In reply to Jakub Jelinek from comment #17) > > That would certainly need : "xmm5" in clobbers (etc.). > And isn't really portable anyway, the compiler can choose to put > anything into %xmm6 in between that and the asm before printf. > But, loading the value from memory into some double temporary (with "=x" for > many of them) > in an asm and then e.g. just "+x" them in empty asms and then comparing > values will likely reproduce it too. > Yes this needs to be polished a bit for automated testing. As explained above, I was using a debugger, so all I wanted to do was to tell the compiler XMM5-XMM15 were clobbered, then it would generate a handler that could recover them (XMM5 is caller-saved so no need to recover it).
