https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100152
--- Comment #9 from lucier at math dot purdue.edu --- (In reply to Iain Sandoe from comment #8) > (In reply to lucier from comment #7) > > (In reply to Iain Sandoe from comment #6) > > > > > yes please - also the original source, if that's OK? > > > > It's highly macrofied C code with a lot of "includes"; is the .i file not > > enough? > > enough for me to replicate the assembly produced, yes. > > would it be possible to set a breakpoint on the function itself and step > through - the reported "invalid insn" seems odd, for sure. I'll look into this---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. > the values of rbp. r10 and esi would be interesting too. This is from the console crash report: Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00007fff924cfba8 rbx: 0x0000000000000001 rcx: 0x000000010e4bdf90 rdx: 0x000000010e4bdca0 rdi: 0x00007ffee1c853a8 rsi: 0x000000000000002f rbp: 0x00007fdf00595ec0 rsp: 0x00007ffee1c853a0 r8: 0x0000000000000460 r9: 0x0000000000000466 r10: 0x00007fff924cfba9 r11: 0x000000010dfab920 r12: 0x0000000000000042 r13: 0x00007ffee1c853f8 r14: 0x000000010e4bdca0 r15: 0x00000000000006d8 rip: 0x000000010dfaf010 rfl: 0x0000000000010206 cr2: 0x000000010dfaea20
