There was no "cripple AMD function". What exists is a check for the ID of the processor. If the check gets an Intel ID, it runs the optimum code for that given series of processor. If it gets anything else, it runs a less optimized code path. The catch here is that the ICC is optimized for specific models, not for specific ISA features.
That is the "Cripple AMD" function. Everyone accepts that VIA is plain slower, so AMD is the only one they'd worry about. If the processor supported the same features, it would still get the unoptimized code paths, if multiple dispatch is allowed.
Beaten with the links. That's what exploring an aquifer-infested embark point (shallow metal
s, deep metal
s, flux, clay, shallow soil, dense plats and trees, calm, and cold...but there's an aquifer taking up much of the middle), and then save-scumming to be able to get aquifer-centric workshop positioning, for the sake of symmetrical fortress design, instead of hopping over to AT forums, will get you .
AFAIK, if you specify the target, it will not check, today, and can still be much faster at vector math than MS--yes, even with an AMD CPU ("can still be," because not everything is crunching on big loops, which are its forte).
Amazingly, it seems as if all the AMD naysayers have lost their voices.
Probably gone hoarse, especially if they've also been over in the PS4 thread...