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 4/4
Date: Thu, 04 Dec 2003 22:45:00 -0000	[thread overview]
Message-ID: <vt2ad68yzia.fsf@zenia.home> (raw)
In-Reply-To: <200312042008.VAA07725@faui1d.informatik.uni-erlangen.de>


Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de> writes:
> this is patch 4/4 to update the s390 backend.
> 
> The focus of this patch is frame handling; it completely removes
> all old-style frame routines and switches the backend to use the
> new frame handling using frame_unwind and frame_base.
> 
> This is still using prologue analysis; in fact the analyser is
> made somewhat more generic: it now understands the new long
> displacement instructions introduced with z990, and it is also
> more flexible in that it can handle unknown instructions 
> intermixed with the prologue due to instruction scheduling.
> Also, literal pool constants are now accepted in 64-bit mode
> as well (not just 31-bit mode).
> 
> This patch removes the last (to my knowledge) use of deprecated
> features in the s390 backend.
> 
> 
> Tested on s390-ibm-linux and s390x-ibm-linux with no new regressions.
> Fixes (about) 23 unexpected and 4 known failures on s390;
> fixes (about) 26 unexpected and 1 known failures on s390x.

This looks great.

For another target, I made the same optimistic assumption you did
about unrecognized instructions, and it worked well.  I did run into
some problems with the analysis going too far, but those were all
exposed by the test suite, so you've probably found everything I did.


      reply	other threads:[~2003-12-04 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 20:08 Ulrich Weigand
2003-12-04 22:45 ` 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=vt2ad68yzia.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