From owner-freebsd-arch Tue May 7 20:21:22 2002 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BBF2237B401; Tue, 7 May 2002 20:21:18 -0700 (PDT) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.3/8.9.1) with ESMTP id g483KrhU002221; Tue, 7 May 2002 20:20:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.3/8.12.3/Submit) id g483Kpc9002220; Tue, 7 May 2002 20:20:51 -0700 (PDT) Date: Tue, 7 May 2002 20:20:51 -0700 (PDT) From: Matthew Dillon Message-Id: <200205080320.g483Kpc9002220@apollo.backplane.com> To: Boris Popov Cc: Poul-Henning Kamp , John Baldwin , arch@FreeBSD.org Subject: Re: syscall changes to deal with 32->64 changes. References: 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, Poul-Henning Kamp wrote: : :> We cannot easily compile for two native APIs if we cannot have two :> different set of 'sys/*' and 'machine/*' files since a lot of the :> types we want to change size on are defined in these files. : : Not exactly, because #ifdefs can handle this perfectly. Performing :diffs on different files is a more simple task though. :... :Boris Popov :http://rbp.euro.ru #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. 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. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message