I'm not sure what behavior with regards to this bug that you're referring to. From what I heard, Intel is freaking out and trying to fix things. Did I miss something?
Notably, the exclusivity-kickback agreements they arranged with several PC manufacturers. https://www.nytimes.com/2017/09/06/business/intel-eu-antitru...
As well as making their compiler choose the slowest execution path possible once it identifies it's running on an AMD/non-Intel CPU. http://www.agner.org/optimize/blog/read.php?i=49#49