From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [rfc]: Replace current_gdbarch in hppa
Date: Mon, 18 Feb 2008 16:04:00 -0000 [thread overview]
Message-ID: <200802181603.m1IG3k9G030893@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <47B999F9.1090608@de.ibm.com> from "Markus Deuling" at Feb 18, 2008 03:45:13 PM
Markus Deuling wrote:
> * hppa-tdep.h (find_global_pointer): Add gdbarch as parameter.
>
> * hppa-hpux-tdep.c (hppa32_hpux_find_global_pointer): Likewise. Replace
> current_gdbarch by gdbarch.
> (hppa64_hpux_find_global_pointer): Likewise.
> * hppa-tdep.c (hppa_find_global_pointer): Likewise.
> (hppa32_push_dummy_call, hppa64_push_dummy_call): Update call for
> find_global_pointer.
>
> * hppabsd-tdep.c (hppabsd_find_global_pointer): Add gdbarch as
> parameter.
> * hppa-linux-tdep.c (hppa_linux_find_global_pointer): Likewise.
>
> * hppa-linux-nat.c (hppa_linux_register_addr): Use ARRAY_SIZE instead
> of gdbarch_num_regs.
>
> * hppa-hpux-tdep.c (hppa_hpux_sr_for_addr): Add gdbarch as parameter and
> replace current_gdbarch by gdbarch.
> (hppa_hpux_push_dummy_code): Update call for hppa_hpux_sr_for_addr.
This is OK, thanks.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-02-18 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 6:48 Markus Deuling
2008-02-15 18:39 ` Ulrich Weigand
2008-02-15 20:19 ` Pedro Alves
2008-02-15 20:22 ` Daniel Jacobowitz
2008-02-18 14:28 ` Markus Deuling
2008-02-18 14:37 ` Ulrich Weigand
2008-02-18 14:47 ` Markus Deuling
2008-02-18 16:04 ` Ulrich Weigand [this message]
2008-02-18 16:12 ` Markus Deuling
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=200802181603.m1IG3k9G030893@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.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