From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] MIPS/ELF: Fixes for external R_MIPS_LITERAL relocations
Date: Wed, 09 Feb 2005 09:23:00 -0000 [thread overview]
Message-ID: <20050209002147.GD6840@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0502071609020.22211@perivale.mips.com>
Maciej W. Rozycki wrote:
> Hello,
>
> According to the SVR4 MIPS ABI supplement and the "64-bit ELF Object File
> Specification" document R_MIPS_LITERAL relocations are only defined for
> local symbols. BFD currently allows them for all symbols.
>
> Here is a fix -- tested for the mips64-linux-gnu, mipsel-linux-gnu and
> mips64el-elf targets with no regressions.
>
> 2005-02-07 Maciej W. Rozycki <macro@mips.com>
>
> * elf32-mips.c (_bfd_mips_elf32_gprel16_reloc): Reject
> R_MIPS_LITERAL relocations for external symbols.
> * elf64-mips.c (mips_elf64_literal_reloc): Likewise.
> * elfn32-mips.c (mips_elf_literal_reloc): Likewise.
>
> OK to apply (or should we have mips_elf_literal_reloc() calling
> _bfd_mips_elf32_gprel16_reloc() after the check for elf32-mips.c now)?
The idea was to give R_MIPS_LITERAL its own handler function because its
values are supposed to get merged. I didn't do so for elf32-mips.c
because there's a weird special casing of _bfd_mips_elf32_gprel16_reloc
in elfxx-mips.c
Btw, R_MIPS16_GPREL seems also to have inconsistencies.
Thiemo
next prev parent reply other threads:[~2005-02-09 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 3:34 Maciej W. Rozycki
2005-02-09 9:23 ` Thiemo Seufer [this message]
2005-02-11 3:50 ` Maciej W. Rozycki
2005-02-11 14:18 ` Thiemo Seufer
2005-02-12 0:24 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050209002147.GD6840@rembrandt.csv.ica.uni-stuttgart.de \
--to=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=binutils@sources.redhat.com \
--cc=macro@mips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).