Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc][2/3] gdbserver bi-arch support: core s390x part
Date: Wed, 27 Feb 2008 03:44:00 -0000	[thread overview]
Message-ID: <200802270342.m1R3gx1j031858@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080226035527.GE4456@caradoc.them.org> from "Daniel Jacobowitz" at Feb 25, 2008 10:55:27 PM

Daniel Jacobowitz wrote:
> You're welcome to prod me when I drop out in the middle of a
> conversation like this.  Really.  I'm sorry about the delay.

Hey, it's no problem ...  I've been busy myself; I would have 
gotten around to pinging you sooner or later ;-)

> On Wed, Jan 30, 2008 at 12:33:33AM +0100, Ulrich Weigand wrote:
> > Yes.  Note that there are two different issues: whether we need
> > to clear the high bit depends on the architecture of gdbserver,
> > but the size of the register depends on the architecture of
> > the inferior.  To simplify the latter issue, maybe it would be
> > nice if generic code had a "collect_register_as_addr" helper
> > that would check the register's size and convert its contents
> > to CORE_ADDR as appropriate?
> 
> Then we'd have room to squabble about whether that function sign
> extended or not.  Let's hold off on this one.

Ah, right.  Fine with me.

> > 	* configure.srv [s390x-*-linux*]: Set srv_regobj to include both
> > 	reg-s390.o and reg-s390x.o.
> > 
> > 	* linux-low.c (new_inferior): New global variable.
> > 	(linux_create_inferior, linux_attach): Set it.
> > 	(linux_wait_for_process): Call the_low_target.arch_setup after the
> > 	target has stopped for the first time.
> > 	(initialize_low): Do not call the_low_target.arch_setup.
> > 
> > 	* linux-s390-low.c (s390_get_pc): Support bi-arch operation.
> > 	(s390_set_pc): Likewise.
> > 	(s390_arch_setup): New function.
> > 	(the_low_target): Use s390_arch_setup as arch_setup routine.
> > 
> > 	* regcache.c (realloc_register_cache): New function.
> > 	(set_register_cache): Call it for each existing regcache.
> 
> This looks great to me.

Thanks, I've checked this in now.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2008-02-27  3:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 17:46 Ulrich Weigand
2008-01-29 20:28 ` Daniel Jacobowitz
2008-01-29 23:35   ` Ulrich Weigand
2008-02-01  0:04     ` Ulrich Weigand
2008-02-26  3:57     ` Daniel Jacobowitz
2008-02-27  3:44       ` Ulrich Weigand [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=200802270342.m1R3gx1j031858@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.org \
    --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