Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
To: cagney@gnu.org (Andrew Cagney)
Cc: weigand@i1.informatik.uni-erlangen.de (Ulrich Weigand),
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Enable DWARF-2 frames on S/390
Date: Thu, 26 Feb 2004 23:03:00 -0000	[thread overview]
Message-ID: <200402262303.AAA00593@faui1d.informatik.uni-erlangen.de> (raw)
In-Reply-To: <403E5DE5.4030409@gnu.org> from "Andrew Cagney" at Feb 26, 2004 03:58:13 PM

Hello Andrew,

> > now that all pieces of the DWARF-2 CFI rework have gone in, and
> > the big s390 backend reorganization was also committed, this patch
> > is the only thing that's missing to enable DWARF-2 frame support
> > on s390.
> > 
> > Do you think a copyright assignment is required for this?  While
> > it's longer than 10 lines, it doesn't really contain anything
> > that should be significant w.r.t. intellectual property -- the
> > s390_dwarf2_frame_init_reg routine only implements the publicly
> > documented s390 ABI calling convention ...
> 
> Can you describe the change with one paragraph of english?

The change consists of installing a dwarf2_frame_set_init_reg
callback that overrides the default register state initializtion
to instead perform the following: set all call-saved registers to 
DWARF2_FRAME_REG_SAME_VALUE, all call-clobbered registers to
DWARF2_FRAME_REG_UNDEFINED, and the virtual PC register to
DWARF2_FRAME_REG_RA.  Which registers count as call-saved vs.
call-clobbered is defined by the Linux for S/390 and Linux for
zSeries ABI documents.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  weigand@informatik.uni-erlangen.de


  reply	other threads:[~2004-02-26 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 16:45 Ulrich Weigand
2004-02-26 20:58 ` Andrew Cagney
2004-02-26 23:03   ` Ulrich Weigand [this message]
2004-02-26 23:48     ` Andrew Cagney
2004-02-27  1:46       ` Ulrich Weigand

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=200402262303.AAA00593@faui1d.informatik.uni-erlangen.de \
    --to=weigand@i1.informatik.uni-erlangen.de \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.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