public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/12990] CFA not tracked in epilogues
Date: Tue, 11 Nov 2003 01:39:00 -0000 [thread overview]
Message-ID: <20031111013930.6952.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031110091239.12990.thh@cyberscience.com>
------- Additional Comments From rth at gcc dot gnu dot org 2003-11-11 01:39 -------
We don't emit CFA information for epilogues at all.
This would be an enhancement to begin doing so.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
GCC build triplet|i686-pc-linux-gnu |
GCC host triplet|i686-pc-linux-gnu |
GCC target triplet|i686-pc-linux-gnu |
Last reconfirmed|0000-00-00 00:00:00 |2003-11-11 01:39:28
date| |
Summary|DWARF frame information |CFA not tracked in epilogues
|gives wrong CFA value in |
|some cases |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12990
next prev parent reply other threads:[~2003-11-11 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 9:12 [Bug debug/12990] New: DWARF frame information gives wrong CFA value in some cases thh at cyberscience dot com
2003-11-10 16:35 ` [Bug debug/12990] " pinskia at gcc dot gnu dot org
2003-11-10 16:39 ` drow at gcc dot gnu dot org
2003-11-11 1:39 ` rth at gcc dot gnu dot org [this message]
[not found] <bug-12990-4@http.gcc.gnu.org/bugzilla/>
2010-10-06 16:26 ` [Bug debug/12990] CFA not tracked in epilogues rth at gcc dot gnu.org
2010-10-06 16:30 ` rth at gcc dot gnu.org
2010-10-06 16:31 ` rth at gcc dot gnu.org
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=20031111013930.6952.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).