My last response.
The processor is stable as proofed by its ability to handle sustained executional benchmarks.
It is proofed by the sheer number of people running the processor w/o issue. Beyond that is software, corner cases, and stateful data issues .. aka caching subsystems.
The issue seems to be segmented to a specific compilation use case which makes it a corner case with assigned internal priority. I went through the thread found here :
https://community.amd.com/thread/215773?start=525&tstart=0 (90% of the people seem to be quite uninformed on how processors function). They hit a corner case issue and are screaming bloody murder. The main execution pipeline seems fine. Where the problem seems to be centered is on OP Caching and other supportive structures...
http://www.anandtech.com/show/10578...lers-micro-op-cache-memory-hierarchy-revealed
Bugs in such optimization subsystems get worked out as they for all processors.
https://github.com/xoreaxeaxeax/sandsifter/blob/master/references/domas_breaking_the_x86_isa_wp.pdf
This is likely why the problem goes away when you disable OP Caching...
I really should get paid to debug issues like this. Who knows, maybe there is something in store for this bug
and no AMD isn't going to disclose anything of note about what the issue is if they've found it and are working on it. This section of the processor doesn't get detailed much. As for other random issues you have (6 WEEKS UPTIME), it's software ... Congrats on 6 weeks uptime.