From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [rfc] [09/09] Get rid of current_gdbarch (gdbarch parameter to legacy_virtual_frame_pointer)
Date: Wed, 07 Nov 2007 07:00:00 -0000 [thread overview]
Message-ID: <4731620F.20905@de.ibm.com> (raw)
In-Reply-To: <200711061745.lA6Hjx1N015175@d12av02.megacenter.de.ibm.com>
Ulrich Weigand schrieb:
> Markus Deuling wrote:
>
>> * gdbarch.sh (legacy_virtual_frame_pointer): Add gdbarch parameter.
>> * gdbarch.{c,h}: Regenerate.
>> * arch-utils.c (legacy_virtual_frame_pointer): Add gdbarch parameter.
>> Replace current_gdbarch by gdbarch.
>> * m32c-tdep.c (m32c_virtual_frame_pointer): Likewise.
>> * mips-tdep.c (mips_virtual_frame_pointer): Likewise.
>> * spu-tdep.c (spu_virtual_frame_pointer): Likewise.
>
> This is OK.
>
> Thanks,
> Ulrich
>
Thank you very much. Committed as well.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
prev parent reply other threads:[~2007-11-07 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 12:23 Markus Deuling
2007-11-05 16:08 ` Ulrich Weigand
2007-11-06 12:03 ` Markus Deuling
2007-11-06 17:46 ` Ulrich Weigand
2007-11-07 7:00 ` Markus Deuling [this message]
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=4731620F.20905@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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