public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: binutils Development <binutils@sourceware.org>
Subject: Re: [Patch] Add private dumper to objdump
Date: Tue, 10 May 2011 02:47:00 -0000	[thread overview]
Message-ID: <20110510024648.GY7018@bubble.grove.modra.org> (raw)
In-Reply-To: <469A65C2-1218-471F-9376-3A9E85C899D8@adacore.com>

On Thu, May 05, 2011 at 04:27:38PM +0200, Tristan Gingold wrote:
> 	* od-xcoff.c: New file.
> 	* objdump.h: New file.
> 	* objdump.c: Include objdump.h
> 	(dump_private_options, objdump_private_vectors): New variables.
> 	(usage): Mention -P/--private.  Display handled options.
> 	(long_options): Add -P/--private.
> 	(dump_target_specific): New function.
> 	(dump_bfd): Handle dump_private_options.
> 	(main): Handle -P.
> 	* doc/binutils.texi (objdump): Document -P/--private.
> 	* configure.in (OBJDUMP_PRIVATE_VECTORS, OBJDUMP_PRIVATE_OFILES):
> 	New variables, compute them.
> 	(od_vectors): Add vectors for private dumpers. Make them uniq.
> 	(OBJDUMP_DEFS): Add OBJDUMP_PRIVATE_VECTORS.
> 	* Makefile.am (HFILES): Add objdump.h
> 	(CFILES): Add od-xcoff.c
> 	(OBJDUMP_PRIVATE_OFILES): New variable.
> 	(objdump_DEPENDENCIES): Append OBJDUMP_PRIVATE_OFILES.
> 	(objdump_LDADD): Ditto.
> 	(EXTRA_objdump_SOURCES): Define.
> 	* Makefile.in: Regenerate.
> 	* configure: Regenerate.

OK.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2011-05-10  2:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 14:29 Tristan Gingold
2011-05-10  2:47 ` Alan Modra [this message]
2011-05-16 12:22   ` Tristan Gingold
2011-05-16 13:36     ` Hans-Peter Nilsson
2011-05-16 13:41       ` H.J. Lu
2011-05-16 13:44         ` Tristan Gingold
2011-05-16 13:48         ` H.J. Lu
2011-05-16 13:50           ` Tristan Gingold
2011-05-16 13:43       ` Tristan Gingold

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=20110510024648.GY7018@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --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).