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.)
|Toshiba expands its budget SSD lineup with its OCZ TL100||8|
|Rumor: Nvidia and Apple may reunite for future Mac GPUs||19|
|Razer Deathadder sheds Chroma skin to achieve Elite status||12|
|Microsoft locks down Edge with virtualization in Win10 Enterprise||20|
|X2 Siryus case maintains a constant 45 degrees||17|
|NZXT joins the tempered-glass party with the S340 Elite||15|
|Lenovo lays off another round of Motorola employees||25|
|EVGA's liquid-cooled GTX 1070 Hybrid card goes up for pre-order||17|
|Google Play Store doors are now open for a few Chrome OS devices||8|