From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14811 invoked by alias); 5 Aug 2003 13:09:17 -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 14801 invoked from network); 5 Aug 2003 13:09:16 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by sources.redhat.com with SMTP; 5 Aug 2003 13:09:16 -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 h75D8XSu028619; Tue, 5 Aug 2003 15:08:33 +0200 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h75D8XRi028618; Tue, 5 Aug 2003 15:08:33 +0200 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Richard Guenther Cc: Matthias Benkmann , gcc@gcc.gnu.org Subject: Re: On inlining in C++ References: From: Gabriel Dos Reis In-Reply-To: Organization: Integrable Solutions Date: Tue, 05 Aug 2003 13:25:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-08/txt/msg00279.txt.bz2 Richard Guenther writes: | The point is, all these "people will optimize" suggestions go against | portability to different compilers. It is going to be non portable only if compiler back ends decide they know better and don't trust the programmer preference. Inline in C++ precisely to cut down the non-portability. Inline in C++ does not mean "hey back-end, optimize this as you want". -- Gaby