From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20344 invoked by alias); 4 Sep 2012 17:17:27 -0000 Received: (qmail 20327 invoked by uid 22791); 4 Sep 2012 17:17:26 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-iy0-f175.google.com (HELO mail-iy0-f175.google.com) (209.85.210.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 04 Sep 2012 17:17:13 +0000 Received: by iaky10 with SMTP id y10so10077375iak.20 for ; Tue, 04 Sep 2012 10:17:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.192.199 with SMTP id hi7mr15035398igc.68.1346779032392; Tue, 04 Sep 2012 10:17:12 -0700 (PDT) Received: by 10.50.5.163 with HTTP; Tue, 4 Sep 2012 10:17:12 -0700 (PDT) In-Reply-To: <50463661.1020303@redhat.com> References: <50243480.7090803@redhat.com> <50254A50.8070208@redhat.com> <50255B35.9020705@redhat.com> <50258712.4070002@redhat.com> <502E6774.8050609@redhat.com> <503F7876.7030606@redhat.com> <503F84A9.8010504@redhat.com> <503F95D8.5010506@redhat.com> <50463661.1020303@redhat.com> Date: Tue, 04 Sep 2012 17:17:00 -0000 Message-ID: Subject: Re: [PATCH] Set correct source location for deallocator calls From: Bryce McKinlay To: Andrew Haley Cc: Dehao Chen , Richard Henderson , Jason Merrill , Richard Guenther , gcc-patches@gcc.gnu.org, David Li , java@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2012-09/txt/msg00006.txt.bz2 On Tue, Sep 4, 2012 at 6:12 PM, Andrew Haley wrote: >> He's also planning to use it for libgo, and other gcc runtime libs >> have indicated interest. It doesn't have to work on all platforms, and >> I can't see how it would be any less portable than addr2line! > > I certainly can. Maybe once it's shaken-down so it's at least as > robust as what we have now it'll be OK. I suspect it hasn't had much > testing with, for example, unwinding through signal handlers. libgcj wouldn't actually use it for unwinding, we already have all that. We'd just use it to read DWARF debug info and give us the source code line numbers.