https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70573
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Problem is that we don't have access to Darwin hardware. Perhaps you could
> get a failing stacktrace via gdb?
(lldb) run
Process 79186 launched:
'/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out' (x86_64)
Process 79186 stopped
* thread #1: tid = 0x29c6013, 0x00007fff9225df06
libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGABRT
frame #0: 0x00007fff9225df06 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
-> 0x7fff9225df06 <+10>: jae 0x7fff9225df10 ; <+20>
0x7fff9225df08 <+12>: movq %rax, %rdi
0x7fff9225df0b <+15>: jmp 0x7fff922587cd ; cerror_nocancel
0x7fff9225df10 <+20>: retq
(lldb) bt
* thread #1: tid = 0x29c6013, 0x00007fff9225df06
libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGABRT
* frame #0: 0x00007fff9225df06 libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x00007fff96b934ec libsystem_pthread.dylib`pthread_kill + 90
frame #2: 0x00007fff880276e7 libsystem_c.dylib`abort + 129
frame #3: 0x00007fff8802785e libsystem_c.dylib`abort_report_np + 181
frame #4: 0x00007fff8804da14 libsystem_c.dylib`__chk_fail + 48
frame #5: 0x00007fff8804d9e4 libsystem_c.dylib`__chk_fail_overflow + 16
frame #6: 0x00007fff8804da7a libsystem_c.dylib`__memset_chk + 37
frame #7: 0x0000000100000f4f a.out`main + 42 at halt_on_error-1.c:12
frame #8: 0x00007fff924055ad libdyld.dylib`start + 1
