From: Richard Henderson <rth@cygnus.com>
To: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
Cc: binutils@sourceware.cygnus.com
Subject: Re: [PATCH] My current SPARC patches
Date: Fri, 16 Jul 1999 14:34:00 -0000 [thread overview]
Message-ID: <19990716143404.A28127@cygnus.com> (raw)
In-Reply-To: <19990709144003.K1736@mff.cuni.cz>
On Fri, Jul 09, 1999 at 02:40:03PM +0200, Jakub Jelinek wrote:
> * bfd/elf64-sparc.c (sparc64_elf_size_dynamic_sections): Remove
> DT_SPARC_PLTFMT.
[...]
> * sparc.h (ELF64_R_TYPE_DATA): Only use ELF64_R_TYPE bits, not
> ELF64_R_SYM bits.
[...]
> * gas/doc/c-sparc.texi: Document .register and .nword pseudo-ops.
[...]
> * bfd/elf64-sparc.c (sparc64_elf_info_to_howto): Use ELF64_R_TYPE_ID.
> (sparc64_elf_get_reloc_upper_bound,
> sparc64_elf_get_dynamic_reloc_upper_bound,
> sparc64_elf_slurp_one_reloc_table, sparc64_elf_slurp_reloc_table,
> sparc64_elf_canonicalize_dynamic_reloc, sparc64_elf_write_relocs):
> New functions.
> (sparc64_elf_check_relocs, sparc64_elf_relocate_section): Use
> ELF64_R_TYPE_ID/DATA where appropriate.
> * gas/config/tc-sparc.c (sparc_ip): Allow OLO10 relocations
> on -64 and not pic.
> (output_insn): Put OLO10's secondary addend into tc_fix_data.
> (md_apply_fix3): Handle BFD_RELOC_SPARC_OLO10.
> (tc_gen_reloc): Return two relocs for OLO10, LO10 and SPARC13.
> * gas/config/tc-sparc.h (RELOC_EXPANSION_POSSIBLE,
> MAX_RELOC_EXPANSION): Define.
> (TC_FIX_TYPE, TC_INIT_FIX_DATA, TC_FIX_DATA_PRINT): Likewise.
All applied.
Thanks.
r~
next prev parent reply other threads:[~1999-07-16 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-05 8:47 [PATCH] Support for R_SPARC_OLO10 relocations Jakub Jelinek
1999-07-08 15:50 ` Richard Henderson
1999-07-09 5:40 ` [PATCH] My current SPARC patches Jakub Jelinek
1999-07-16 14:34 ` Richard Henderson [this message]
1999-07-08 16:09 ` [PATCH] Support for R_SPARC_OLO10 relocations Richard Henderson
1999-07-08 20:02 ` Ian Lance Taylor
1999-07-08 23:34 ` Jakub Jelinek
1999-07-09 9:52 ` Ian Lance Taylor
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=19990716143404.A28127@cygnus.com \
--to=rth@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
/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).