https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #34 from dave.anglin at bell dot net --- On 2019-07-04 4:43 p.m., elowe at elowe dot com wrote: > Could the problem be with "AS"? > > Maybe that assembler is technically ok, but AS is generating bad machine code? That's easy to check. You can dump the assembler output generated by gcc with "-S" option. I'm pretty sure the faulting gprel instruction is from gcc. You can compare .o files generated by new and working compiles with cmp. You can disassemble .o and executables with "objdump -d". You can link .o file generated with new compiler with old compiler. You can also test using HP and GNU tools. Use "gcc -save-temps -v" to capture intermediate files and commands. I think the issue is more likely with ld than as.