From: Alan Modra <amodra@bigpond.net.au>
To: Paul Brook <paul@codesourcery.com>
Cc: binutils@sources.redhat.com
Subject: Re: [patch] PPC small data symbols.
Date: Wed, 29 Jun 2005 06:47:00 -0000 [thread overview]
Message-ID: <20050629064650.GB28975@bubble.grove.modra.org> (raw)
In-Reply-To: <200506290222.40944.paul@codesourcery.com>
On Wed, Jun 29, 2005 at 02:22:40AM +0100, Paul Brook wrote:
> * bfd-in.h (_bfd_elf_provide_symbol): Update prototype.
> * bfd-in2.h: Regenerate.
> * elf32-ppc.c (ppc_elf_set_sdata_syms): Make sdata symbols section
> relative.
> * elflink.c (bfd_elf_set_symbol): Add section argument.
> (_bfd_elf_provide_symbol): Ditto.
> (_bfd_elf_provide_section_bound_symbols): Pass NULL section argument.
OK.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-06-29 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 1:22 Paul Brook
2005-06-29 6:47 ` Alan Modra [this message]
2005-07-12 11:25 ` Alan Modra
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=20050629064650.GB28975@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--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).