From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28113 invoked by alias); 18 Dec 2007 13:15:31 -0000 Received: (qmail 28094 invoked by uid 22791); 18 Dec 2007 13:15:30 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Dec 2007 13:15:24 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 452282A963E; Tue, 18 Dec 2007 08:15:22 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id w7yVI8x-wAMu; Tue, 18 Dec 2007 08:15:22 -0500 (EST) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by rock.gnat.com (Postfix) with ESMTP id 1CFF82A9637; Tue, 18 Dec 2007 08:15:21 -0500 (EST) Message-ID: <4767C7E1.8030707@adacore.com> Date: Tue, 18 Dec 2007 13:29:00 -0000 From: Robert Dewar User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Alexandre Oliva CC: Joe Buck , Geert Bosch , Daniel Berlin , Diego Novillo , Mark Mitchell , Ian Lance Taylor , Richard Guenther , gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: Designs for better debug info in GCC References: <4749DE66.1090602@codesourcery.com> <4756B02D.9010302@google.com> <4aca3dc20712151903r46c9eceane35edb92d08240ac@mail.gmail.com> <4aca3dc20712161712w1133fb96qd66be0e9a0bb1716@mail.gmail.com> <20071217012735.GA9275@synopsys.com> <8DF14649-456C-40D6-94C5-DC3285EFD7C2@adacore.com> <20071218012438.GD2908@synopsys.com> <476765C7.5050106@adacore.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00518.txt.bz2 Alexandre Oliva wrote: > On Dec 18, 2007, Robert Dewar wrote: >> OK, so you are agreeing that good debuggability is impossible >> with all the optimizations in place, so once again, let's have >> an optimziation level that optimizes as far as possible without >> harming debuggability. > > I don't oppose such an optimization level, even though I don't know > that we agree on what "good debuggability" stands for. My definition is that it should be indistinguishable from -O0 except that I could live without being able to modify variables. > > It's just that changing optimizations is precisely *against* the goals > of my current project. So, don't expect significant efforts to this > end from me at this time. But you can't achieve the above criterion with your approach.