From: Nick Clifton <nickc@cambridge.redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH]
Date: Thu, 06 Dec 2001 02:26:00 -0000 [thread overview]
Message-ID: <m3bshcd4w9.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <20011205144708.A676@sunsite.ms.mff.cuni.cz>
Hi Jakub,
> 2001-12-05 Jakub Jelinek <jakub@redhat.com>
>
> * elf.c (_bfd_elf_rela_local_sym): Only call
> _bfd_merged_section_offset if merge_info is non-NULL.
> (_bfd_elf_rel_local_sym, _bfd_elf_section_offset): New.
> * elf-bfd.h (_bfd_elf_rel_local_sym, _bfd_elf_section_offset): New
> prototypes.
> * elf32-arm.h (elf32_arm_final_link_relocate): Use
> _bfd_elf_section_offset.
> (elf32_arm_relocate_section): Use _bfd_elf_rel_local_sym.
> * elf32-i386.c (elf_i386_relocate_section): Use
> _bfd_elf_section_offset and _bfd_elf_rel_local_sym.
> * elf32-sh.c (sh_elf_relocate_section): Likewise.
> * elf32-sparc.c (elf32_sparc_relocate_section): Use
> _bfd_elf_section_offset.
> * elf32-cris.c (cris_elf_relocate_section): Likewise.
> * elf32-hppa.c (elf32_hppa_relocate_section): Likewise.
> * elf32-i370.c (i370_elf_relocate_section): Likewise.
> * elf32-m68k.c (elf_m68k_relocate_section): Likewise.
> * elf32-mips.c (mips_elf_create_dynamic_relocation): Likewise.
> * elf32-ppc.c (ppc_elf_relocate_section): Likewise.
> * elf32-s390.c (elf_s390_relocate_section): Likewise.
> * elf64-alpha.c (elf64_alpha_relocate_section): Likewise.
> * elf64-ppc.c (ppc64_elf_relocate_section): Likewise.
> * elf64-s390.c (elf_s390_relocate_section): Likewise.
> * elf64-sparc.c (sparc64_elf_relocate_section): Likewise.
> * elf64-x86-64.c (elf64_x86_64_relocate_section): Likewise.
> * elfxx-ia64.c (elfNN_ia64_install_dyn_reloc): Likewise.
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2001-12-06 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 5:44 [PATCH] Jakub Jelinek
2001-12-06 2:26 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 7:20 [PATCH] Joshi, Tejas Sanjay
2022-10-28 8:15 ` [PATCH] Jan Beulich
2022-10-28 15:45 ` [PATCH] H.J. Lu
2022-10-31 4:37 ` [PATCH] Joshi, Tejas Sanjay
2022-10-31 9:37 ` [PATCH] Jan Beulich
2009-04-02 4:56 [PATCH] Peter Bergner
2009-04-02 7:01 ` [PATCH] Alan Modra
2003-04-28 17:50 problems re: makeinfo '--split-size' arg? cgd
2003-04-28 18:55 ` Joseph S. Myers
[not found] ` <mailpost.1051556216.2781@news-sj1-1>
2003-05-01 17:27 ` cgd
2003-05-02 6:23 ` Gerald Pfeifer
2003-05-02 21:44 ` [patch] cgd
2000-02-09 20:39 [PATCH] Andrew Cagney
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=m3bshcd4w9.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=binutils@sources.redhat.com \
--cc=jakub@redhat.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).