Shintai
Supreme [H]ardness
- Joined
- Jul 1, 2016
- Messages
- 5,678
Man you are just trying to be obtuse. I never said the library or ability to execute X87 wasn't there but that it was being blocked. FX processors weren't running X87 but were instead running it with SSE2 (how it was told 3 years ago) which explains the speed differential. Also it was said the block was to circumvent paying Intel for the X87 license. Not a bad call considering the only real issue with it was Skyrim as it seemed to be the lone software left using it other than HWBot. And that is how it works by the by. If the code is X87 and the processor doesn't support it then the active code on the processor will run the code, a legacy support if you will, so no it will not crash, well as long as the supported code has the legacy support which most will.
And for the love of all that is holy, try reading a post and attempt to comprehend. It doesn't matter if one were 4 core and the other 82 core, the comparison was for IPC/single core throughput. Number of cores is irrelevant until we start talking multithread computation.
You cant run x87 code with SSE2. I think you confuse the point that AMD wanted to replace x87 in 64bit mode with SSE2. The Intel licensing part is also utter BS to put it gently. Since its all part of the cross licensing agreement. When instructions are a defacto standard, there isn't any form of other path around it.
Construction cores could and have always been able to run native x87 code since day 1. Anything else is utter rubbish. You have as well provided absolutely no proof of your claims. But instead rejected evidence with even more fairy tale excuses.
http://support.amd.com/TechDocs/26569_APM_v5.pdf
At this point I think we have to agree on disagreeing.
Last edited: