From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10889 invoked by alias); 3 Aug 2008 07:28:22 -0000 Received: (qmail 10880 invoked by uid 22791); 3 Aug 2008 07:28:21 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out3.apple.com (HELO mail-out3.apple.com) (17.254.13.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 03 Aug 2008 07:27:39 +0000 Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id CEA4435242BE; Sun, 3 Aug 2008 00:27:36 -0700 (PDT) Received: from relay14.apple.com (unknown [127.0.0.1]) by relay14.apple.com (Symantec Mail Security) with ESMTP id A8C2F28092; Sun, 3 Aug 2008 00:27:36 -0700 (PDT) X-AuditID: 11807134-a79fcbb000000ece-85-48955de837dc Received: from [17.116.196.165] (unknown [17.116.196.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay14.apple.com (Apple SCV relay) with ESMTP id 59F7828087; Sun, 3 Aug 2008 00:27:36 -0700 (PDT) Cc: Diego Novillo , Bill Maddox , gcc@gcc.gnu.org, Jason Merrill Message-Id: From: Chris Lattner To: Mark Mitchell In-Reply-To: <4893234E.1040400@codesourcery.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Subject: Re: [lto] C++. streaming, front-end specific tree nodes, IR types, and assembler names Date: Sun, 03 Aug 2008 07:28:00 -0000 References: <8a0e66f0808010033s39e22020q1bf4ed0ed9bee71e@mail.gmail.com> <4893234E.1040400@codesourcery.com> X-Mailer: Apple Mail (2.926) X-IsSubscribed: yes 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: 2008-08/txt/msg00027.txt.bz2 On Aug 1, 2008, at 7:53 AM, Mark Mitchell wrote: > My concern is that the path we're heading towards is: ... > 2. Middle-end builds call graphs, etc., and throws out 99.5% of the > functions and debug info, after deciding it's not needed. (Note, > for example, that mangled names are typically not needed for inline > functions.) Note that you often still need the mangled form of a symbol name when inlined if -g is present. -Chris