public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw" <Richard.Earnshaw@arm.com>
To: <paul@codesourcery.com>, <binutils@sources.redhat.com>
Cc: "Daniel Jacobowitz" <drow@false.org>
Subject: RE: Don't use STT_ARM_TFUNC for final links
Date: Fri, 19 Nov 2004 19:24:00 -0000	[thread overview]
Message-ID: <89A528FE6DB0FA44877BB2F05B8467180160FE24@ZIPPY.Emea.Arm.com> (raw)

> 2004-11-19  Paul Brook  <paul@codesourcery.com>
> 
> bfd/
>  * elf32-arm.c (elf32_arm_swap_symbol_in): New function.
>  (elf32_arm_swap_symbol_out): New function.
>  (elf32_arm_size_info): Add.
>  (elf_backend_size_info): Define.
> ld/
>  * testsuite/ld-arm/mixed-lib.sym: Update for THUMB_FUNC change.
> 

OK.

R.

             reply	other threads:[~2004-11-19 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 19:24 Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-18 20:03 Richard Earnshaw
2004-11-19 15:49 ` Paul Brook

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=89A528FE6DB0FA44877BB2F05B8467180160FE24@ZIPPY.Emea.Arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=binutils@sources.redhat.com \
    --cc=drow@false.org \
    --cc=paul@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).