From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30033 invoked by alias); 17 Dec 2002 12:33:44 -0000 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 Received: (qmail 29982 invoked from network); 17 Dec 2002 12:33:40 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by 209.249.29.67 with SMTP; 17 Dec 2002 12:33:40 -0000 Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id gBHCRKtv007037; Tue, 17 Dec 2002 13:27:20 +0100 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id gBHCRKHh007036; Tue, 17 Dec 2002 13:27:20 +0100 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Jan Hubicka Cc: David Edelsohn , Zack Weinberg , gcc@gcc.gnu.org, libstdc++@gcc.gnu.org Subject: Re: basic-improvements merge status References: <200212162226.RAA23850@makai.watson.ibm.com> <20021217085445.GU3138@kam.mff.cuni.cz> <20021217113450.GA25435@kam.mff.cuni.cz> From: Gabriel Dos Reis In-Reply-To: <20021217113450.GA25435@kam.mff.cuni.cz> Organization: Integrable Solutions Date: Tue, 17 Dec 2002 08:39:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-12/txt/msg01032.txt.bz2 Jan Hubicka writes: | > Jan Hubicka writes: | > | > | -fno-builtin-sin does the trick. | > | > The issue isn't about the lack of built-in sin. It is about lack of | > support (either hardwired or in library) for sin{, f,l}. | | libstdc++ does provide these. All we need is to move them into libgcc | and use -fno-builtin-sin to compile file in question. | What do you see wrong about using the -fno-builtin to compile runtime | support that must be done in a way breaking C90 standard? My grip about -fno-builtin is that it operates (at least that is my understanding) in a yes/no mode whereas in practice we need something that can understand gray variation. That is, the builtins are not all missing at the same time; we should be able to make the compiler understand that. -- Gaby