From: Alan Modra <amodra@gmail.com>
To: DJ Delorie <dj@redhat.com>
Cc: gingold@adacore.com, binutils@sourceware.org
Subject: Re: [rfc] new bfd hook: additional link map text
Date: Wed, 07 May 2014 03:02:00 -0000 [thread overview]
Message-ID: <20140507030239.GY16139@bubble.grove.modra.org> (raw)
In-Reply-To: <201405061515.s46FFnQk025221@greed.delorie.com>
On Tue, May 06, 2014 at 11:15:49AM -0400, DJ Delorie wrote:
>
> > > Why not adding a new field in ld_emulation_xfer_struct ? Looks lighter.
> >
> > Attached, mostly. Git is giving me a diff relative to the previous patch.
I think the idea is good. I'm assuming the previous patch won't be
going in, nor the debug printfs. :) The place to declare
rx_additional_link_map_text is in a new bfd/elf32-rx.h file, included
by both ld/emultempl/rxelf.em and bfd/elf32-rx.c, assuming the latter
is where you'll define the function.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2014-05-07 3:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 2:14 DJ Delorie
2014-04-11 7:10 ` Tristan Gingold
2014-04-22 20:55 ` DJ Delorie
2014-05-06 15:15 ` DJ Delorie
2014-05-07 3:02 ` Alan Modra [this message]
2014-05-07 3:13 ` DJ Delorie
2014-05-10 2:33 ` DJ Delorie
2014-05-27 15:53 ` DJ Delorie
2014-05-27 16:20 ` Nicholas Clifton
2014-05-27 21:16 ` DJ Delorie
2014-05-28 13:13 ` Alan Modra
2014-05-27 22:04 ` Breakage with "[rfc] new bfd hook: additional link map text" Hans-Peter Nilsson
2014-05-27 23:06 ` DJ Delorie
2014-06-03 15:43 ` [rfc] new bfd hook: additional link map text Maciej W. Rozycki
2014-06-03 15:58 ` DJ Delorie
2014-06-03 16:20 ` Maciej W. Rozycki
2014-06-03 16:25 ` DJ Delorie
2014-06-03 20:25 ` DJ Delorie
2014-06-04 11:56 ` Maciej W. Rozycki
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=20140507030239.GY16139@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=gingold@adacore.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).