public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 10 Feb 2005 14:07:00 -0000	[thread overview]
Message-ID: <1108032219.4376.21.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <420A67CF.2090802@codesourcery.com>

On Wed, 2005-02-09 at 19:43, Julian Brown wrote:
> Hi,
> 
> This version of the patch uses BFD_RELOC_NONE instead of 
> BFD_RELOC_ARM_NONE, and changes the existing use of BFD_RELOC_NONE in 
> gas/config/tc-arm.c to use BFD_RELOC_UNUSED instead to prevent conflict.
> 
> Tested on arm-none-eabi and i686-pc-linux-gnu.
> 
> OK?
> 
> ChangeLog:
> 
>      * gas/config/tc-arm.c (do_t_ldmstm): Change BFD_RELOC_NONE to
>      BFD_RELOC_UNUSED.
>      (do_t_push_pop): Likewise.
>      (md_assemble): Likewise.
>      (md_apply_fix3): Handle BFD_RELOC_NONE, make BFD_RELOC_UNUSED same
>      as previous meaning of BFD_RELOC_NONE.
>      (create_unwind_entry): Output dependency on the required personality
>      routines.
>      * gas/testsuite/gas/arm/unwind.d: Alter expected output to include
>      dependency on __aeabi_unwind_cpp_pr[01].

OK.

R.

  reply	other threads:[~2005-02-10 10:47 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 [this message]
2005-02-09 17:12 ` Richard Earnshaw

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=1108032219.4376.21.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).