Pretty interesting that they have been providing µCode updates for those crappy Bobcat APUs, especially when they did not provide one to fix the critical issues which Bulldozers had... I guess it would require some activity from AMD side too in order to MS be able to distribute the updates in the first place
This is not the same as testing different code paths of existing and well known CPU heavy software. But as forcing a specific FFT size to be used for hours is more than running the built in standard tests, this might simply have been missed.
Talking about Processor bugs, I was just googling around info about the POPAD bug, which affected mostly Intel and AMD 386s. Fixes were done compiler side, and applications similar to what CPU-Z is today, back at that time, actually RELIED on trying to reproduce specific bugs to figure out what specific Processor it was.
Asus just launched BIOS 1602 for the Z170-A, which I have. As always, Asus is vague about what's fixed ("stability improvements"), but it appears to include the new CPU microcode. I've run some tests (Cinebench, 7-zip, Sunspider and Geekbench) and at least in those tests there are no performance regressions. Running AVX code is perhaps the most interesting test and I'm not sure if any of the above mentioned use AVX... Does anyone know?