From owner-freebsd-arch Tue May 7 20:28:16 2002 Delivered-To: freebsd-arch@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by hub.freebsd.org (Postfix) with ESMTP id 8578737B411; Tue, 7 May 2002 20:28:11 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id D6C5028CD6; Wed, 8 May 2002 10:28:08 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id C5F1C28CD5; Wed, 8 May 2002 10:28:08 +0700 (ALMST) Date: Wed, 8 May 2002 10:28:08 +0700 (ALMST) From: Boris Popov To: Matthew Dillon Cc: Poul-Henning Kamp , John Baldwin , arch@FreeBSD.org Subject: Re: syscall changes to deal with 32->64 changes. In-Reply-To: <200205080320.g483Kpc9002220@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 7 May 2002, Matthew Dillon wrote: > #ifdef's are a bad idea for this case IMHO, at least in regards to > being able to develop the new ABI without interfering with the > release schedule. I think it is far less dangerous and far more > advantageous to simply give each ABI it's own secondary include > (-I) path (not to mention making the include files far more readable > post-ABI-changes). There is absolutely no need to pollute the include > files with #ifdefs. Yes, this is what I'm expressed in the "performing diffs" phrase :) > Also we should consider the fact that it may take considerably longer > for many ports to become 64-bit time_t safe (not to mention uids, gids, > and so forth). Doing the ABI properly with a compiler option and default > setting would allow unsafe ports to be compiled to the old ABI on > new systems. The power of this capability should not be underestimated. Heh, different ABI in the different ports is the real fun of it. -- Boris Popov http://rbp.euro.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message