Hi Thomas,
Summary: it's the combination of an optimization flag (-O) with debugging
symbols (-g) that fails.
So, after all, maybe it's more a gcc issue than a binutils issue?
Almost certainly. The bug is probably that gcc is generating a short
version of a branch instruction (on instruction sequence) when it should
be producing a long version instead. Probably because it has
incorrectly calculated the lengths of the instructions between the
source and destination of the branch.
Cheers
Nick
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
