[15/*] This directive could do some things, like limit reordering, try to translate intrinsics as directly as possible, etc., with an emphasis on _predictability_ rather than speed.
(As an aside, I also doubt this would be something you'd do for AMD CPUs. It would more be something to do for the tranche of Intel CPUs that drastically downclocked the code when ymm's were used. But regardless, CLANG didn't accomplish that in the buggy codegen.)
-
-
You are right, this does not appear to be related to any optimisation trade-off to prevent slow-256 code paths, rather just an optimizer bug. Personally I would cut the Clang people some slack though, it’s a massively complex thing that works extremely well most of the time ;-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.