Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [just for the record]: new prologue analyzer for S/390
Date: Mon, 21 Apr 2003 16:31:00 -0000	[thread overview]
Message-ID: <3EA41CE6.9000706@redhat.com> (raw)
In-Reply-To: <vt2r87zmpwm.fsf@zenia.red-bean.com>

> I think this patch shouldn't be committed; I'm just posting it for
> reference.
> 
> This patch implements a new prologue analyzer for the S/390.  It's
> meant to be general enough to handle the complex prologues GCC emits
> on the S/390, and robust enough to tolerate compiler changes.  In my
> experience, it does pretty well, even on optimized code.
> 
> However, the S/390 GDB folks at IBM and I agree that GDB on the S/390
> should move towards using Dwarf 2 CFI and location lists whenever
> possible, and do only minimal prologue analysis to handle those few
> common cases where Dwarf 2 CFI is not available.  And it looks to me
> as if the work needed in GDB's core code to make it possible for any
> target to use Dwarf 2 CFI is almost complete.  In that light, it
> doesn't make sense to dump a new, large, complex prologue analyzer
> into the code base that will soon be eclipsed by a better solution.

It is important to ensure that all technical decisions related to GDB 
are discussed here, in this forum.  Issues, specific to this change, 
that come to mind, include:

- the unpredictability of the CFI timetable (a bird in the hand vs ...)

- the unpredictability of the legal processes sometimes required before 
accepting changes (must assume that the change doesn't exist)

- the need to get the existing s390's frame code updated so that it 
implements frame-unwind (this is in addition, and largely orthogonal to 
the missing generic CFI unwinder).  Ignoring s390_get_signal_frame_info, 
which should be separated out, the attached appears to only affect the 
prologe analyzer so is relatively independant?

- the need to have gdb behave reasonably well when there is no, or 
minimal, debug info

- the need to fix the s390 problem of having a wrong frame ID . 
stack_addr (does this change address that problem?)

- what tests it actually fixes (data?)

> This patch assumes that IBM's s390x ABI patch has been applied.  That
> patch is currently working its way through the IBM/FSF IP process.
> http://sources.redhat.com/ml/gdb-patches/2003-02/msg00097.html

To be honest, I don't understand the dependency.  This patch modifies 
the prologue analysier while the other change appears to be fixing the 
push_arguments function.  While they might interact in positive ways, I 
don't think that they are dependant.

I'd also strongly recommend putting your the file / changes through 
gdb_indent.sh - GNU indent will likely have a field day on the 
formatting of the comments :-(

Andrew



  reply	other threads:[~2003-04-21 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 21:53 Jim Blandy
2003-04-21 16:31 ` Andrew Cagney [this message]
2003-04-21 16:38   ` Daniel Jacobowitz
2003-04-21 21:11     ` Andrew Cagney
2003-04-21 21:54   ` Jim Blandy
2003-05-04 22:11 ` 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=3EA41CE6.9000706@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.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