From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Julian Brown <julian@codesourcery.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Indicate dependency on personality routines for ARM EHABI
Date: Wed, 09 Feb 2005 17:12:00 -0000 [thread overview]
Message-ID: <1107967189.4376.6.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <420A38B6.3010609@codesourcery.com>
On Wed, 2005-02-09 at 16:22, Julian Brown wrote:
> Hi,
>
> This patch causes gas to emit dependencies on personality routines
> (__aeabi_unwind_cpp_pr[012]) from a suitable run-time library when
> necessary, using an R_ARM_NONE relocation type.
>
> Tested on i686-pc-linux-gnu and arm-none-eabi with no regressions
> (though the expected output for the .ARM.extab has changed for one of
> the tests.)
>
> OK to apply?
>
> ChangeLog:
>
> * bfd/bfd-in2.h (bfd_reloc_code_real): New relocation type
> (BFD_RELOC_ARM_NONE).
> * bfd/elf32-arm.c (elf32_arm_reloc_map): BFD_RELOC_ARM_NONE maps to
> R_ARM_NONE.
> * bfd/libbfd.h (bfd_reloc_code_): Add BFD_RELOC_ARM_NONE.
> * bfd/reloc.c (BFD_RELOC_ARM_NONE): Add.
> * gas/config/tc-arm.c (md_apply_fix3): Handle BFD_RELOC_ARM_NONE.
> (tc_gen_reloc): Handle BFD_RELOC_ARM_NONE.
> (create_unwind_entry): Output dependency on the unwinding routines.
> * gas/testsuite/gas/arm/unwind.d: Alter expected output to include
> dependency on __aeabi_unwind_cpp_pr[01].
bfd-in2.h is a generated file. Rather than your above ChangeLog entry
you should just log it as regenerated.
It's not necessary to include patches to generated files when sending a
changeset, just note that it has been rebuilt.
OK apart from that.
R.
prev parent reply other threads:[~2005-02-09 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 17:06 Julian Brown
2005-02-09 17:09 ` Ian Lance Taylor
2005-02-09 17:24 ` Paul Brook
2005-02-09 17:32 ` Ian Lance Taylor
2005-02-09 19:43 ` Andreas Schwab
2005-02-09 17:28 ` Richard Earnshaw
2005-02-09 17:42 ` Ian Lance Taylor
2005-02-09 18:26 ` Richard Earnshaw
2005-02-09 19:02 ` Julian Brown
2005-02-09 20:27 ` Ian Lance Taylor
2005-02-09 20:35 ` Richard Earnshaw
2005-02-09 21:48 ` Julian Brown
2005-02-09 22:21 ` Julian Brown
2005-02-10 14:07 ` Richard Earnshaw
2005-02-09 17:12 ` Richard Earnshaw [this message]
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=1107967189.4376.6.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=binutils@sources.redhat.com \
--cc=julian@codesourcery.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).