Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: gdb-patches@sources.redhat.com, uweigand@de.ibm.com
Subject: Re: [PATCH] S/390 port modernization 1/4
Date: Thu, 04 Dec 2003 21:18:00 -0000	[thread overview]
Message-ID: <vt2vfowz3kf.fsf@zenia.home> (raw)
In-Reply-To: <200312042006.VAA07701@faui1d.informatik.uni-erlangen.de>


The rearrangement of the register code looks great.  I did core file
register handling in Not The Right Fashion, and your new code seems to
fix that.  And it's more legible.

It seems like s390-nat.c's s390_gregset_regmap and
s390_fpregset_regmap are essentially the same information as
s390-tdep.c's s390_regmap_gregset, s390x_regmap_gregset, and
s390_regmap_fpregset, except that the s390 / s390x distinction is
static in s390-nat.c, and dynamic in s390-tdep.c.  But if I recall
correctly, the way the types in the kernel header files work out, the
core dump format is always the same as the PTRACE uarea format.

Would it be possible to have s390-nat.c simply use the structures from
s390-tdep.c?  There's nothing wrong with having an s390-tdep.h file in
the gdb directory; that's the usual arrangement for native systems.

But this is a minor issue.  Given the nature of the IBM / FSF process,
feel free to either revise this patch, or submit it as a separate
patch, whichever is easiest for you.


  parent reply	other threads:[~2003-12-04 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 20:06 Ulrich Weigand
2003-12-04 21:01 ` Jim Blandy
2003-12-04 21:56   ` Ulrich Weigand
2003-12-05  4:21     ` Jim Blandy
2003-12-04 21:18 ` Jim Blandy [this message]
2003-12-04 21:45   ` Ulrich Weigand
2003-12-05  4:29     ` Jim Blandy
2003-12-04 21:43 ` Jim Blandy
2003-12-04 22:11   ` Ulrich Weigand
2003-12-05  4:30     ` Jim Blandy

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=vt2vfowz3kf.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=uweigand@de.ibm.com \
    --cc=weigand@i1.informatik.uni-erlangen.de \
    /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