From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22201 invoked by alias); 29 Jul 2003 12:04:32 -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 22179 invoked from network); 29 Jul 2003 12:04:30 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by sources.redhat.com with SMTP; 29 Jul 2003 12:04:30 -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 h6TC4HSu013746; Tue, 29 Jul 2003 14:04:17 +0200 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h6TC4HJr013745; Tue, 29 Jul 2003 14:04:17 +0200 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Richard Guenther Cc: gcc@gcc.gnu.org Subject: Re: std::pow implementation References: From: Gabriel Dos Reis In-Reply-To: Organization: Integrable Solutions Date: Tue, 29 Jul 2003 12:38:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-07/txt/msg01966.txt.bz2 Richard Guenther writes: | for my scientific app. If this ends up the same way as the | __attribute__((leafify)) discussion, I'll stop complaining now and instead | just file a PR for the record. I bet your application will benefit much more from a better inlining support in the compiler than obfuscating the library. (Note that it need not be a sophisticated inliner). We get to that point because, at some point it was decided that the compiler knows better than the programmer. -- Gaby