http://sourceware.org/bugzilla/show_bug.cgi?id=12771
--- Comment #7 from Jonathan Nieder <jrnieder at gmail dot com> 2011-06-29 15:35:40 UTC --- (In reply to comment #6) > This seems far more likely to be a problem in the tools used to build gold, > rather than a problem in gold itself. I'm going to close this out. Please > reopen if you have some reason to believe that there is a problem in gold > itself. Just for completeness: did you test on a non-emulated ARM system? The triggered failed assertion says bool found = object->merge_map()->get_output_offset(NULL, input_shndx, input_offset, &output_offset); // If this assertion fails, it means that some relocation was // against a portion of an input merge section which we didn't map // to the output file and we didn't explicitly discard. We should // always map all portions of input merge sections. gold_assert(found); That doesn't immediately scream "code generation bug" to me --- it could be a use of uninitialized memory or some other portability problem. If I wanted to pin it on something other than gold this early, I'd be more likely to blame libstdc++ than the code generation, but it's hard to learn anything without hardware to investigate on. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils