From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22846 invoked by alias); 6 Aug 2003 02:20:11 -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 22746 invoked from network); 6 Aug 2003 02:20:10 -0000 Received: from unknown (HELO piper.synopsys.com) (198.182.56.5) by sources.redhat.com with SMTP; 6 Aug 2003 02:20:10 -0000 Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id h762JNF02032; Tue, 5 Aug 2003 19:19:23 -0700 Date: Wed, 06 Aug 2003 02:47:00 -0000 From: Joe Buck To: Andrew Pinski Cc: Geoff Keating , Gabriel Dos Reis , aph@redhat.com, coyote@coyotegulch.com, gcc@gcc.gnu.org Subject: Re: On inlining in C++ Message-ID: <20030805191923.A2019@synopsys.com> References: <20030805190007.A1778@synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from pinskia@physics.uc.edu on Tue, Aug 05, 2003 at 10:15:05PM -0400 X-SW-Source: 2003-08/txt/msg00329.txt.bz2 > > Ah, but even if we fix the inlining issues, we still aren't keeping the > > promise: inline functions are still slower in many cases if > > struct/class > > objects with more than one member are passed by reference. On Tue, Aug 05, 2003 at 10:15:05PM -0400, Andrew Pinski wrote: > (but that macro is not equivalent to that function). Yes, you can nitpick it, but the effect is real.