From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gdb-patches@sources.redhat.com
Cc: cagney@gnu.org, randolph@tausq.org
Subject: Re: [patch/rfa/hppa] Use frame pointer for unwinding
Date: Mon, 17 May 2004 16:13:00 -0000 [thread overview]
Message-ID: <200405171613.i4HGDEEV005885@hiauly1.hia.nrc.ca> (raw)
> > Anyway, I spoke with Dave Anglin (hppa gcc maintainer) about this. The
> > problem is that currently gcc/binutils does not correctly implement the
> > alloca_frame bit. The frame pointer is maintained in the case of a
> > variable-sized frame, but there is no flag set in the unwind record, and
> > the frame layout is slightly different compared to the HP compiler. It's
> > one of the things that should be fixed in gcc eventually. Also Dave has
> > observed that the Save_SP bit is set only for gcc; with the HP compiler
> > this is not set. Finally, with the HP compiler the frame pointer can be
> > maintained either in r3 or r4. It's not clear yet how this works. Some
> > more experimentation/disassembling HP code is required :-( I will add
> > some comments to the code about this situation.
>
> Is there a GCC bug report for this?
No. GCC has always used a different frame layout than HP and set
Save_SP to indicate that the frame has a frame pointer. Whether it
is a bug to not set the alloca_frame bit is an open question given
the different layout.
Ada uses the HP unwind library to a limited extent for backtraces. I
believe that the frame marker support that GCC provides for the saved
SP value is sufficient for the library to unwind an alloca frame
without the alloca_frame bit being set. We only do this under hpux
for compatibility with the HP library.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next reply other threads:[~2004-05-17 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 16:13 John David Anglin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-17 17:14 John David Anglin
2004-05-17 17:28 ` Randolph Chung
2004-05-17 17:54 ` John David Anglin
2004-05-16 2:07 Randolph Chung
2004-05-16 10:36 ` Mark Kettenis
2004-05-16 15:36 ` Randolph Chung
2004-05-16 16:22 ` Mark Kettenis
2004-05-16 16:42 ` Randolph Chung
2004-05-16 16:32 ` Andrew Cagney
2004-05-16 17:03 ` Randolph Chung
2004-05-17 0:13 ` Randolph Chung
2004-05-17 2:34 ` Randolph Chung
2004-05-17 15:23 ` Andrew Cagney
2004-05-17 16:01 ` Randolph Chung
2004-05-17 17:27 ` Andrew Cagney
2004-05-17 15:13 ` Andrew Cagney
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=200405171613.i4HGDEEV005885@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.org \
/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