From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23357 invoked by alias); 15 Oct 2008 20:22:07 -0000 Received: (qmail 23189 invoked by uid 48); 15 Oct 2008 20:20:44 -0000 Date: Wed, 15 Oct 2008 20:22:00 -0000 Message-ID: <20081015202044.23188.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug debug/33429] debug info for class2 in g++.dg/other/unused1.C requires -femit-class-debug-always In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mmitchel at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-10/txt/msg01026.txt.bz2 ------- Comment #7 from mmitchel at gcc dot gnu dot org 2008-10-15 20:20 ------- The comment in the test says: /* Make sure we didn't eliminate casted types because we thought they were unused. */ If we don't want to do that any more, I think we can just remove this test, rather than passing it special options. But, I think it's odd if I'm in the debugger, looking at code that says: return (X*)y; if I can't say "print (X*)y". If the type is coming from a library, we may not ever create objects of this type. Finally, we use vast amounts of space in object files for debug info, since we emit the same debug info in multiple object files. Trying to optimize by not emitting debug info in this case doesn't seem likely to be a big win given our overall strategy. I don't have any data to support that claim, though. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33429