From: Thiemo Seufer <ths@networkno.de>
To: binutils@sourceware.org
Subject: [PATCH] Fix MIPS16 stub calling relocations
Date: Fri, 09 Jun 2006 14:13:00 -0000 [thread overview]
Message-ID: <20060609135134.GA12079@networkno.de> (raw)
Hello All,
I committed the appended patch, it makes sure a (32bit) call stub to
MIPS16 code is called with the proper relocation type.
Thiemo
2006-06-09 David Ung <davidu@mips.com>
* bfd/elfxx-mips.c (mips_elf_calculate_relocation): Fix mode for stub
calling relocations.
Index: bfd/elfxx-mips.c
===================================================================
RCS file: /cvs/src/src/bfd/elfxx-mips.c,v
retrieving revision 1.170
diff -u -p -r1.170 elfxx-mips.c
--- bfd/elfxx-mips.c 8 Jun 2006 23:51:25 -0000 1.170
+++ bfd/elfxx-mips.c 9 Jun 2006 12:55:16 -0000
@@ -4074,6 +4074,8 @@ mips_elf_calculate_relocation (bfd *abfd
}
symbol = sec->output_section->vma + sec->output_offset;
+ /* The target is 16-bit, but the stub isn't. */
+ target_is_16_bit_code_p = FALSE;
}
/* If this is a 16-bit call to a 32- or 64-bit function with a stub, we
need to redirect the call to the stub. */
reply other threads:[~2006-06-09 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060609135134.GA12079@networkno.de \
--to=ths@networkno.de \
--cc=binutils@sourceware.org \
/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).