Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ulrich Weigand <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: jimb@red-bean.com (Jim Blandy), gdb@sourceware.org
Subject: Re: Prologue analysis interface
Date: Wed, 23 Nov 2005 14:54:00 -0000	[thread overview]
Message-ID: <200511231452.jANEq3Qh015156@53v30g15.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20051123020455.GA2247@nevyn.them.org> from "Daniel Jacobowitz" at Nov 22, 2005 09:04:55 PM

Daniel Jacobowitz wrote:

> The S/390 code is a lot less clear-cut than the m32c, not surprisingly.
> Most of the tangly bits are related to frameless functions.  Some of
> this could be further commonized too, but for now my suggested plan
> above should work for this also.

Note that some of the heuristics is actually wrong.  I hope to be able
to update the s390 prolog analyzer soon to simplify it a bit and fix
some of the issues I've found.  Unfortunately I cannot guarantee I'll
find time to do so right now ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  Linux on zSeries Development
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2005-11-23 14:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 19:30 Jim Blandy
2005-11-22 19:44 ` Daniel Jacobowitz
2005-11-23  0:20   ` Jim Blandy
2005-11-23  2:14     ` Daniel Jacobowitz
2005-11-23  2:52       ` Joel Brobecker
2005-11-23  3:52         ` Jim Blandy
2005-11-23 16:56           ` Ulrich Weigand
2005-11-23 18:37             ` Joel Brobecker
2005-11-24  6:21               ` Jim Blandy
2005-11-24 10:21             ` Jim Blandy
2005-11-24 17:18               ` Ulrich Weigand
2005-11-25  3:06                 ` Jim Blandy
2005-11-23  3:14       ` Jim Blandy
2005-11-23  6:18         ` Daniel Jacobowitz
2005-11-23 14:54       ` Ulrich Weigand [this message]
2006-01-27 17:11 ` Daniel Jacobowitz
2006-01-27 18:25   ` Jim Blandy
2006-01-28 13:40     ` 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=200511231452.jANEq3Qh015156@53v30g15.boeblingen.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jimb@red-bean.com \
    /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