https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100152
--- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> --- I have to try and figure out a way to be able to reproduce the run-time error. Yes, the assembler output is different between 10.2 and 10.3 - but that insn is not apparently in error (and I checked that the assembler gives the same bit pattern for it with GAS and LLVM - it would probably have been astonishing if that was wrong... but) Is there a usable work-around while we try to figure this out? - what happens if you remove "-fschedule-insns2" ? You mentioned that "the way the program is called is not simple, it's a Scheme->C compiler building a "module", so it's hidden behind a number of scripts." I assume it is not some kind of JIT? FWIW, I don't believe that there were Darwin-specific changes to scheduling and insn output between 10.2 and 10.3, although it is possible that some other change exposed a latent problem, of course. Do you know if this failure persists with a trunk or 11 branch compiler? (sorry for all the questions, but since I can't actually reproduce the runtime fail yet)
