This is the mail archive of the
mailing list for the binutils project.
Re: building glibc with gold linker & -frecord-gcc-switches results in internal error
- From: Ian Lance Taylor <iant at google dot com>
- To: Cary Coutant <ccoutant at google dot com>
- Cc: Per Ãyvind Karlsen <peroyvind at mandriva dot org>, binutils <binutils at sourceware dot org>
- Date: Tue, 14 Feb 2012 13:22:22 -0800
- Subject: Re: building glibc with gold linker & -frecord-gcc-switches results in internal error
- References: <CA+0WU1SqJgWb74moznhKa7_LwPgYQQWh0ZsYv62_Bgx_twETaw@mail.gmail.com> <email@example.com> <CA+0WU1R2DJCSALj2FaPOHC1+DfojXjXV-JGXcwN3qK_kRDJkiw@mail.gmail.com> <CAHACq4pREHCw3hxY8sj3aurO-WBoaN5Fd5sGH=XAMaNooZ7ghw@mail.gmail.com>
Cary Coutant <firstname.lastname@example.org> writes:
> I'm not sure what to make of this. I think it clearly doesn't make
> sense to have those relocations in a string merge section, so I'd
> think the right thing to do here is to fix gold so that it prints an
> error instead of asserting.
> Ian, what do you think?
Would the error be about a GOT32 relocation in a non-allocated section?
Or would it be about an unrecognized relocation in a string merge
section? I can't quite decide if we should give an error for either of
those cases or whether we should try to handle them as best we can.
Obviously an error is better than a crash.
And obviously it would be good to figure out what gcc is doing to create
those relocations, and try to fix that.