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 (updated)
Date: Fri, 05 Dec 2003 04:59:00 -0000	[thread overview]
Message-ID: <vt2ekvjyi7w.fsf@zenia.home> (raw)
In-Reply-To: <200312050154.CAA07985@faui1d.informatik.uni-erlangen.de>


Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de> writes:
> this is a revised version of patch 1/4 to update the s390 backend.
> It incorporates the following changes:
> 
> - Mention SKIP_TRAMPOLINE_CODE (tm-linux.h) in ChangeLog.
> - Add a s390-tdep.h file to hold register numbers and regmap declarations.
> - Export regmap arrays from s390-tdep.c and reuse them from s390-nat.c
> - Allocate struct regset objects statically.
> - Update copyright dates as appropriate.
> 
> Retested on s390-ibm-linux and s390x-ibm-linux with no new
> regressions.

Looks great to me.


      reply	other threads:[~2003-12-05  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  1:54 Ulrich Weigand
2003-12-05  4:59 ` Jim Blandy [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=vt2ekvjyi7w.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