• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Does the Hammer do floating point differently?

zephyrprime

Diamond Member
I've read the the Hammer can use the SSE registers for regular (not SIMD) floating point operations, freeing mankind from the horror of the x87 floating point stack. Is this true? I've not been able to find any confirming data sources online.
 
This is probably better in the "highly technical" section. I don;t think there are any hammer white papers floating around, but I could be wrong (obviously, microsoft and suse have one)
 
This is an interesting concept although I doubt it. Programs make direct calls to register addresses. If you change where data is stored, the program would still treat it as if it were in the x87 register stack. It'd still make numerous useless FXCH calls and only operate on the top of the stack.
 
Is there a way to loopback to the next instruction when a pointless call (i.e. FXCH) in the code is made, thereby shaving off unecessay time wasted for a reload of the pipeline caused by the pointless call?
 
Not really neccessary with the Athlon design. It uses a barrel shift method that allows FXCH instructions to be executed without any (or at least, noticable) loss in performance. Although such an idea would help the P4 significantly.
 
Back
Top