public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info
Date: Sun, 02 Jan 2005 20:29:00 -0000 [thread overview]
Message-ID: <20050102202954.17110.qmail@sourceware.org> (raw)
In-Reply-To: <20041222003609.19124.hjl@lucon.org>
------- Additional Comments From dberlin at gcc dot gnu dot org 2005-01-02 20:29 -------
Patch coming.
This is also a latent bug forever in gcc.
We've been generating fbreg for a lot of things we shouldn't, we just never
noticed before now because it didn't try to evaluate them at runtime unless you
outputted location lists.
Thus, it simply statically converted the location expression fbregs into
something it could evaluate, regardless of whether there was a real frame base
or not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124
next prev parent reply other threads:[~2005-01-02 20:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 0:36 [Bug debug/19124] New: " hjl at lucon dot org
2004-12-22 0:53 ` [Bug debug/19124] " hjl at lucon dot org
2004-12-22 1:09 ` hjl at lucon dot org
2004-12-22 1:12 ` pinskia at gcc dot gnu dot org
2004-12-22 1:34 ` pinskia at gcc dot gnu dot org
2004-12-22 13:07 ` steven at gcc dot gnu dot org
2004-12-26 0:56 ` dberlin at gcc dot gnu dot org
2004-12-28 2:34 ` pinskia at gcc dot gnu dot org
2004-12-28 18:39 ` hjl at lucon dot org
2004-12-28 18:49 ` dberlin at dberlin dot org
2004-12-30 3:38 ` hjl at lucon dot org
2004-12-30 5:10 ` dberlin at dberlin dot org
2004-12-30 21:01 ` hjl at lucon dot org
2005-01-02 20:29 ` dberlin at gcc dot gnu dot org [this message]
2005-01-04 20:07 ` ac131313 at redhat dot com
2005-01-10 16:45 ` dberlin at dberlin dot org
2005-01-10 18:32 ` dberlin at gcc dot gnu dot org
2005-01-10 18:55 ` hjl at lucon dot org
2005-01-10 22:37 ` hjl at lucon dot org
2005-01-20 20:10 ` cvs-commit at gcc dot gnu dot org
2005-01-20 20:15 ` dberlin at gcc dot gnu dot 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=20050102202954.17110.qmail@sourceware.org \
--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).