[mips patch RFC] removal of gas embedded-pic support code
Daniel Jacobowitz
drow@false.org
Thu May 6 02:26:00 GMT 2004
More information about the Binutils mailing list
Thu May 6 02:26:00 GMT 2004
- Previous message (by thread): [mips patch RFC] removal of gas embedded-pic support code
- Next message (by thread): GAS embedded-PIC reloc removal vs. mips-linux exception handling
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 05, 2004 at 09:30:18PM +0100, Richard Sandiford wrote: > Daniel Jacobowitz <drow@false.org> writes: > >On Wed, May 05, 2004 at 01:15:55PM -0700, cgd@broadcom.com wrote: > >> I'd say that the mips64-linux-gnu version is the "better" one, since > >> the PC-relative 32/64 relocations were non-standard. > > Agreed. > > >> But I have no idea how much pain would be caused by switching. Or > >> whether (and how much) backward-compatibility needs to be maintained. > > > > No compatibility needs to be maintained for this, AFAIK. > > I guess it depends on how much lock-in is acceptable between binutils > and gcc. The patch to make mips*-linux-gnu use pc-relative EH entries > went in over two years ago (17-Feb-02, it seems). And even the latest > gcc release will try to use them. > > If we remove support entirely, it won't be possible for users to upgrade > beyond 2.15 without also upgrading to a newer compiler and recompiling > all their old C++ objects. What I meant was that the change in GCC didn't affect backwards compatibility, sorry. I agree that we're stuck with the reloc for a bit. -- Daniel Jacobowitz
- Previous message (by thread): [mips patch RFC] removal of gas embedded-pic support code
- Next message (by thread): GAS embedded-PIC reloc removal vs. mips-linux exception handling
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list