Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933323AbZAQXnr (ORCPT ); Sat, 17 Jan 2009 18:43:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753463AbZAQXni (ORCPT ); Sat, 17 Jan 2009 18:43:38 -0500 Received: from terminus.zytor.com ([198.137.202.10]:52358 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752318AbZAQXnh (ORCPT ); Sat, 17 Jan 2009 18:43:37 -0500 Message-ID: <49726C56.6080905@zytor.com> Date: Sat, 17 Jan 2009 15:40:06 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Linus Torvalds CC: Kyle McMartin , Ingo Molnar , Mikael Pettersson , Linux Kernel Mailing List Subject: Re: "eliminate warn_on_slowpath()" change causes many gcc-3.2.3 warnings References: <200901171519.n0HFJZuf028704@harpo.it.uu.se> <20090117161817.GA10825@elte.hu> <49723912.6020108@zytor.com> <20090117204421.GA1700@bombadil.infradead.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 948 Lines: 31 Linus Torvalds wrote: > > Don't do this. That just forces a load off a complex pointer instead, with > no upsides. At least if it was > > extern const char warn_slowpath_nofmt[]; > > it would only load the pointer itself, which is still a fairly expensive > op, but at least doesn't require the extra memory load. > > But you'd be better off jusst making it something like > > #define NO_FMT ((const char *)(-1)) > > instead, which is really much more obvious, and doesn't need any of that > "get a pointer" overhead. > At least on x86, the two ops should be the same cost? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/