Re: Ouch
AMD puts the blame on the hardware that implements the MULX instruction being intensively used, leading to local overheating. There could be some firmware solution which tries to keep multiply instructions as far apart on the execution pipeline as possible, or have the compiler alternate between those floating point registers which are physically the furthest apart to spread the heat, or even have the firmware distribute multiplications to different physical registers while keeping the formal address the same.