From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15356 invoked by alias); 8 Dec 2007 11:25:26 -0000 Received: (qmail 15322 invoked by uid 22791); 8 Dec 2007 11:25:25 -0000 X-Spam-Check-By: sourceware.org Received: from smtp.nildram.co.uk (HELO smtp.nildram.co.uk) (195.112.4.54) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 08 Dec 2007 11:25:17 +0000 Received: from firetop.home (85-211-134-127.dyn.gotadsl.co.uk [85.211.134.127]) by smtp.nildram.co.uk (Postfix) with ESMTP id D364C2B5905; Sat, 8 Dec 2007 11:25:11 +0000 (GMT) Received: from richard by firetop.home with local (Exim 4.63) (envelope-from ) id 1J0xo1-00037V-DK; Sat, 08 Dec 2007 11:25:13 +0000 From: Richard Sandiford To: Rask Ingemann Lambertsen Mail-Followup-To: Rask Ingemann Lambertsen ,Mark Mitchell , GCC Patches , fortran@gcc.gnu.org, java-patches@gcc.gnu.org, rsandifo@nildram.co.uk Cc: Mark Mitchell , GCC Patches , fortran@gcc.gnu.org, java-patches@gcc.gnu.org Subject: Re: Link tests after GCC_NO_EXECUTABLES References: <87d4tqu4nv.fsf@firetop.home> <20071201115252.GS17368@sygehus.dk> <20071201120251.GT17368@sygehus.dk> <20071201223447.GU17368@sygehus.dk> <47531F54.6010802@codesourcery.com> <20071205172224.GM17368@sygehus.dk> <47574456.1070108@codesourcery.com> <20071206175819.GO17368@sygehus.dk> <87abomzqvw.fsf@firetop.home> <20071207151759.GQ17368@sygehus.dk> Date: Sat, 08 Dec 2007 11:25:00 -0000 In-Reply-To: <20071207151759.GQ17368@sygehus.dk> (Rask Ingemann Lambertsen's message of "Fri\, 7 Dec 2007 16\:17\:59 +0100") Message-ID: <87prxh77ja.fsf@firetop.home> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00383.txt.bz2 Rask Ingemann Lambertsen writes: > On Fri, Dec 07, 2007 at 11:27:31AM +0000, Richard Sandiford wrote: >> OK, I'm not doing a good job of staying out of this discussion as >> promised, but I was hoping someone else would raise this point... >> >> My main concern with applying this patch in its current state is that, >> while we have (intentionally) only been talking about *-elf so far, >> newlib != *-elf. Cygwin is also an important newlib user, and I don't >> remember anyone explicitly mentioning it so far in this thread. > > What is a good way of detecting the bare-metal targets? *-elf*, *-eabi*? TBH, I'm not sure. I wonder if a good starting point might be to take the toplevel configure.ac stanzas that currently (i.e. after your earlier patch) set libgloss_dir, and see which of those have an appropriate "bare-metal-like" configuration in newlib/libgloss. That might be easier than a full two-way comparison between toplevel configure and newlib/libgloss, and it can always be added to later. (On that note, it might be a good idea to introduce a specific mips*-*-elf* stanza in the toplevel makefile, and only do the ibgloss_dir stuff, or its replacement, for that. The current mips*-*-* stanza traps almost-certainly-bitrotten targets like mips*-openbsd* as well.) I see downthread that you and Mark talked about a new configure option. Would it be worth defaulting to on for the targets we know are "safe"? (For the record, I do like the cache idea, and thanks for implementing it. I hope yesterday's message didn't make it sound otherwise. I just wanted to make sure that what went into mainline wouldn't cast the net too wide. Once we identify targets that work with the cache, I'd personally like them to use it by default. And that includes the mips*-elf* family.) Richard