From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17131 invoked by alias); 2 Jan 2005 20:29:56 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 17111 invoked by uid 48); 2 Jan 2005 20:29:54 -0000 Date: Sun, 02 Jan 2005 20:29:00 -0000 Message-ID: <20050102202954.17110.qmail@sourceware.org> From: "dberlin at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041222003609.19124.hjl@lucon.org> References: <20041222003609.19124.hjl@lucon.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info X-Bugzilla-Reason: CC X-SW-Source: 2005-01/txt/msg00146.txt.bz2 List-Id: ------- 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