Remember I used the beta. Sad to say some of the optimizations that were apparent actually made the real code run slightly slower - it was a beta remember - so I fell back on my own experience. I'm sure the newer versions are better. It is a free download from AMD. They even sent me a pocket knife and a fashlight for being a beta tester. The pocket knife is particularly useful for prying intel motherboards out of rack units, seems to have been designed for the purpose. . . .
When I used CodeAnalyst it was test and repeat. I don't know about newer versions. I'd like to hear your experience.
The trade off in this stuff is accuracy v. speed. I needed to do a completely compliant conversion. FP is the only way to go. You are right for jpeg display - who cares as long as there are no visible artifacts but when you are doing repeated conversion cycles, well then accuracy is all.
Integer will always be preferable to fp in x86 machines, the cost of an integer -> fp conversion is high. Scaled integer and FP need not be exclusive. I left out of my explanation of MMX vs FP that a lot of the special case optimization code, like all black blocks, is always integer.
News 
Market Data 
Discover 
AI
