From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 991 invoked by alias); 30 Jul 2003 14:01:04 -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 984 invoked from network); 30 Jul 2003 14:01:03 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by sources.redhat.com with SMTP; 30 Jul 2003 14:01:03 -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 h6UE0kSu021779; Wed, 30 Jul 2003 16:00:46 +0200 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h6UE0k6N021778; Wed, 30 Jul 2003 16:00:46 +0200 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: dewar@gnat.com (Robert Dewar) Cc: martin@MPA-Garching.MPG.DE, gcc@gcc.gnu.org Subject: Re: std::pow implementation References: <20030730135250.D230EF2DFE@nile.gnat.com> From: Gabriel Dos Reis In-Reply-To: <20030730135250.D230EF2DFE@nile.gnat.com> Organization: Integrable Solutions Date: Wed, 30 Jul 2003 14:10:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-07/txt/msg02167.txt.bz2 dewar@gnat.com (Robert Dewar) writes: | > But this implies an "inline" directive | > which would more or less _force_ the compiler to always inline the code. | | Yes, but there is nothing in the standard or in common sense that requires | you to treat this implicit inline the same way you would treat other inlines, there is nothing like "implicit" inline and other inlines in C++. -- Gaby