Looks like AMD might have another CPU erratum on its hands.
DragonFly BSD creator Matthew Dillon wrote about the problem (and outlined his debugging efforts) last December. Yesterday, Dillon said he received confirmation from AMD that the issue he reported is, indeed, due to an erratum. His latest posting includes the following quote, attributed to AMD:
"AMD has taken your example and also analyzed the segmentation fault and the fill_sons_in_loop code. We confirm that you have found an erratum with som e [sic] AMD processor families. The specific compiled version of the fill_sons_in_loop code, through a very specific sequence of consecutive back-to-back pops and (near) return instructions, can create a condition where the process or incorrectly updates the stack pointer."
Dillon managed to reproduce the problem on systems with Phenom II X4 820 and Opteron 6168 processors. According to his December posting, the erratum leads to "a segmentation fault, bus fault, or other fault related to corrupt program state, causing the compiler to report an internal compiler failure." Dillon witnessed the problem when running the cc1 compiler from the gcc-4.4.7 system. (Thanks to Slashdot for the links.)
|Corsair Lighting Node Pro brings light strip control to every PC||4|
|In the lab: Asus' Tinker Board SBC||1|
|In the lab: HyperX's Alloy FPS mechanical gaming keyboard||3|
|Team Group Cardea SSDs are ready to handle the heat||2|
|Gigabyte's Ryzen motherboards are home, home on the range||6|
|Zotac molds GTX 1050s into low-profile tiny terrors||0|
|TR forums spotlight: krazyredboy's crazy simulator PC||8|
|Deals of the week: a high-end Mini-ITX mobo, fast RAM, storage, and more||24|
|Steam Audio SDK promises better surround sound gratis||13|
|Best part of the article? We're flying home with Ryzen review samples as of this writing.||+42|