On 3/24/2012 12:19 PM, Brad Roberts wrote:
I saw this sort of behavior in the auto-tester (was win7 at the time,
At least I'm not losing my mind :-)
now it's running on a windows server 2008 box) during the various combinations of compilation options until I switched to adding a counter and a suffix to each compilation output. I don't recall there being a particular pattern to the failures (like being tied to array ops).
More investigation: If I delete the array ops, but add the import: import core.cpuid; it fails. I'm also running a 6 core AMD FX 6100 CPU.
