5 ms·
GenuineIntel moment.
by orlp 1y ago
GenuineIntel moment.
- hofrogs 1y agoI'm interested in that story, what are you referring to with "GenuineIntel"?
- orlp 1y agoIntel's C++ compiler is known to add branches in its generated code checking if the CPU is "GenuineIntel" and if not use a worse routine: https://en.wikipedia.org/wiki/Intel_C%2B%2B_Compiler#Support_for_non-Intel_processors https://en.wikipedia.org/wiki/Intel_C%2B%2B_Compiler#Support....
- pieterbreed 1y agoIs this for the runtime of the compiled code or for the compiling machine? Do they generate slow code if the compiler is running on non-intel?
- SSLy 1y agothe runtime. patching cpuid makes the code go faster
- kstrauser 1y agoFor the compiled code. Its output deliberately runs slower on non-Intel CPUs.
- Uvix 1y agoRuntime of the compiled code. The ostensible intent is so that new processors can use new features like SIMD, while offering a fallback for older ones. In practice, they’re detecting an Intel processor, not just the specific feature.
- microtonal 1y agoAlso MKL: https://danieldk.eu/Intel-MKL-on-AMD-Zen https://danieldk.eu/Intel-MKL-on-AMD-Zen
- bayindirh 1y agoEven in the middle of that turmoil, we managed to compile some code with Intel's ICC and make it go faster on AMD Opterons, breaking Intel's own numbers. When my colleague said that they managed to go faster than intel with icc with some hand tuned parameters, I remember answering "youdidwat?". Good times.
- reitzensteinm 1y agoOr maybe Quack III: Arena. https://m.slashdot.org/story/21054 https://m.slashdot.org/story/21054
- iforgotpassword 1y agoI think that was the first case (to go public), but I remember reading about this in game magazines a couple times after this, for both ATI and nvidia.
- BoredPositron 1y agoNow I want a Quake shooter but with ducks.
- carlos22 1y agoNot ducks, but chickens, was very popular in Germany back in the day: https://en.wikipedia.org/wiki/Crazy_Chicken https://en.wikipedia.org/wiki/Crazy_Chicken
- avhception 1y agoOh wow, that was a blast from the past. The Moorhuhn craze! Many people, including me, didn't have an internet connection back in the day. The Sneakernet went into overdrive so get everyone a copy!
- supportengineer 1y agoA Duck Hunt, if you will…
- deleted 1y ago[deleted]
- dahauns 1y agoAah, that brings back memories... Interestingly, most benchmark controversies back in the day are now expected behaviour, i.e. game-specific optimizations with no (well, in this age of upscalers and other lossy optimization techniques, probably even somewhat) visible image degradation. A gaming-specific driver with no game-specific improvements in its changelog would be considered strange, and it very much works with executable detection. Back in the day, there was still the argument that drivers should not optimize for benchmarks even when visually identical, because it wouldn't show the hardware's real world potential. Kinda cute from today's perspective. :) But of course there were the obvious cases... The Quack3 lowering filtering quality as shown above, of course (at least that one was put into the driver as a togglable setting later on). But the most cheeky one has to be nVidia's 3dmark03 "optimizations", where they blatantly put static clip planes into the scenes so that everything outside the predefined camera path from the benchmark sequence would simply be cut from the scene early (which e.g. fully broke the freelook patched into 3dmark and would generally break any interactive application)
- _zoltan_ 1y ago[flagged]