From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9272 invoked by alias); 20 Dec 2007 16:41:22 -0000 Received: (qmail 9257 invoked by uid 22791); 20 Dec 2007 16:41:22 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 20 Dec 2007 16:41:12 +0000 Received: from zps76.corp.google.com (zps76.corp.google.com [172.25.146.76]) by smtp-out.google.com with ESMTP id lBKGeHDH004855; Thu, 20 Dec 2007 08:40:17 -0800 Received: from smtp.corp.google.com (spacemonkey1.corp.google.com [192.168.120.115]) by zps76.corp.google.com with ESMTP id lBKGeDI0018832 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Dec 2007 08:40:14 -0800 Received: from localhost.localdomain.google.com (adsl-76-249-168-94.dsl.pltn13.sbcglobal.net [76.249.168.94]) (authenticated bits=0) by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id lBKGe31S030310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Dec 2007 08:40:08 -0800 To: Alexandre Oliva Cc: "Daniel Berlin" , "Diego Novillo" , "Mark Mitchell" , "Robert Dewar" , "Richard Guenther" , gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: Designs for better debug info in GCC References: <47671BF4.5050704@google.com> <4aca3dc20712181415y3d5c3717s6d73b1335b311313@mail.gmail.com> <4aca3dc20712182207y648f7bbhab9e0af8ad2ff832@mail.gmail.com> <4aca3dc20712190759g748d6e15pa0e5146c3f5ca0ba@mail.gmail.com> <4aca3dc20712191240r472ee46ekacf32886a1abd63@mail.gmail.com> From: Ian Lance Taylor Date: Thu, 20 Dec 2007 17:04:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg01009.txt.bz2 Alexandre Oliva writes: > > How do i know i need to change this DEBUG expression. > > As reassoc looks for sets of variables it can freely mess with, it > should take note of variables that are used in debug annotations in > addition to the kind of single (?) non-debug uses it's interested in, > such that, when it modifies these variables, the annotations can be > compensated for. The question is how it finds them efficiently, without doing a scan of all instructions. Ian