From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264871AbUFAR1x (ORCPT ); Tue, 1 Jun 2004 13:27:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264877AbUFAR1x (ORCPT ); Tue, 1 Jun 2004 13:27:53 -0400 Received: from fw.osdl.org ([65.172.181.6]:15039 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S264871AbUFAR1w (ORCPT ); Tue, 1 Jun 2004 13:27:52 -0400 Date: Tue, 1 Jun 2004 10:27:16 -0700 (PDT) From: Linus Torvalds To: Mikael Pettersson cc: "H. Peter Anvin" , linux-kernel@vger.kernel.org Subject: Re: [PATCH][2.6.6-rc3] gcc-3.4.0 fixes In-Reply-To: <16572.38987.239160.819836@alkaid.it.uu.se> Message-ID: References: <200404292146.i3TLkfI0019612@harpo.it.uu.se> <16572.38987.239160.819836@alkaid.it.uu.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 1 Jun 2004, Mikael Pettersson wrote: > > You're assuming pointers have uniform representation. Are we? I don't see any point where we cast any function pointers to anything else. We cast data pointers all over the place, but that is actually guaranteed to work in C for some "large enough" integer type, and "unsigned long" is pretty much it. And even function pointers should be safeish. The fact that some broken architecture (can you say "ia64"?) has totally idiotic calling conventions and requires the caller to load the GP value is _their_ problem. The architecture will either die or hide the fact that it's being silly. For now it's hiding it. Repeat after me: practice is more important than theory. A _lot_ more important. Linus