Please take some time to look at these and determine if they are real problems or can be ignored. Having the buildbots green at the time we branch is the main goal!
Pay close attention to buildbot failures! If you check-in something and one of the buildbots breaks, please either fix is quickly or revert the patch until a fix can be submitted.
With your help, we will have a very smooth 3.0 release.
I was able to reproduce the problem, but only during a parallel make of the entire llvm-gcc tree and not consistently. I have not been able to reproduce yet with a single build step, which is making this quite painful.
I did carefully inspect all of the differences between the .o files and proved to myself that they are functionally equivalent. It appears to be random codegen behavior. But I don't understand yet why self-hosting the front end could affect it.
Duncan, if you provide the differing .o files I can take a look and see if I notice a pattern. Better yet, provide an address-stripped asm diff in case my binutils are inadequate. We can move this discussion to PR11133.
You mentioned that you need a loaded system to reproduce it. I agree, but can't understand the relationship between system load and codegen. Addresses are randomized either way.
