From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15624 invoked by alias); 30 Sep 2009 20:33:08 -0000 Received: (qmail 15470 invoked by uid 48); 30 Sep 2009 20:32:56 -0000 Date: Wed, 30 Sep 2009 20:33:00 -0000 Subject: [Bug lto/41529] New: LTO configuration should detect if the target is ELF X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dnovillo at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg02803.txt.bz2 >>From http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02106.html > You enable LTO by default if a suitable libelf is found. But what if > libelf is present but the target for which GCC is being configured is not > an ELF target? Presumably LTO will not work in that case (i.e., it > requires the target to be an ELF target rather than producing ELF files > separate from the normal objects for that target)? So shouldn't LTO be > disabled for non-ELF targets even when libelf is present? We discussed a > patch to do that back in May (e.g. > ); what happened > to that? (On the whole I think a blacklist of targets that are (a) > supported by GCC and (b) not ELF is better than trying to list all ELF > targets. Certainly various ELF targets are missing from the list used to > set is_elf for --enable-gold.) -- Summary: LTO configuration should detect if the target is ELF Product: gcc Version: lto Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: dnovillo at gcc dot gnu dot org ReportedBy: dnovillo at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41529