From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Strip the ISA bit when printing symbol offsets
Date: Mon, 28 Dec 2009 21:12:00 -0000 [thread overview]
Message-ID: <20091228211222.GB30551@caradoc.them.org> (raw)
In-Reply-To: <20091113222444.GB4557@adacore.com>
On Fri, Nov 13, 2009 at 02:24:44PM -0800, Joel Brobecker wrote:
> > 2009-11-13 Daniel Jacobowitz <dan@codesourcery.com>
> >
> > * defs.h (print_address_symbolic, build_address_symbolic): Update
> > prototypes.
> > * printcmd.c (print_address_symbolic): Take a gdbarch argument.
> > Pass it to build_address_symbolic. All callers updated.
> > (build_address_symbolic): Take a gdbarch argument. Use
> > gdbarch_addr_bits_remove for functions. All callers updated.
>
> I tried to find something wrong with this, but couldn't :).
> So, no objection.
Thanks. I've belatedly committed this.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-12-28 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 21:27 Daniel Jacobowitz
2009-11-13 22:25 ` Joel Brobecker
2009-12-28 21:12 ` Daniel Jacobowitz [this message]
2009-11-14 9:28 ` Eli Zaretskii
2009-11-14 15:47 ` Daniel Jacobowitz
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=20091228211222.GB30551@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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