From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16737 invoked by alias); 17 Nov 2005 21:40:01 -0000 Received: (qmail 16724 invoked by uid 22791); 17 Nov 2005 21:39:59 -0000 Received: from yosemite.airs.com (HELO yosemite.airs.com) (205.217.158.180) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Thu, 17 Nov 2005 21:39:59 +0000 Received: (qmail 23987 invoked by uid 10); 17 Nov 2005 21:39:57 -0000 Received: (qmail 16414 invoked by uid 500); 17 Nov 2005 21:39:50 -0000 To: Richard Earnshaw Cc: gcc mailing list Subject: Re: Link-time optimzation References: <437BB214.1070306@codesourcery.com> <20051117011900.GA17847@redhat.com> <437BDC9E.3080608@codesourcery.com> <1132227692.24110.40.camel@pc960.cambridge.arm.com> From: Ian Lance Taylor Date: Thu, 17 Nov 2005 21:40:00 -0000 In-Reply-To: <1132227692.24110.40.camel@pc960.cambridge.arm.com> 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 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2005-11/txt/msg00790.txt.bz2 Richard Earnshaw writes: > We spend a lot of time printing out the results of compilation as > assembly language, only to have to parse it all again in the assembler. > Given some of the problems this proposal throws up I think we should > seriously look at bypassing as much of this step as possible, and of > generating object files from directly in the compiler. Ultimately we'd > only need to parse assembly statements for inline asm constructs. I certainly think that is a good idea, and it is one which has been discussed before. But I think this is really a separate issue which should not be confused with the link time optimization proposal. I think the symbol table issues are a red herring. The only troublesome case is when using both a non-GNU assembler and a non-GNU debugger, and even then the worst case is some difficulty with naming static functions and variables (we can rename them using a suitable mangled source file name as a suffix so that it is still possible to find them, albeit awkward). I think that if we lay down an appropriate trail, other tool developers will follow soon enough. Ian