From owner-freebsd-current Wed May 27 17:30:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15856 for freebsd-current-outgoing; Wed, 27 May 1998 17:30:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA15808 for ; Wed, 27 May 1998 17:30:38 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 19834 invoked by uid 505); 28 May 1998 00:29:28 -0000 Date: 28 May 1998 00:29:28 -0000 Message-ID: <19980528002928.19833.qmail@m2.findmail.com> From: "Brian Feldman" Subject: Replacing gcc as the system compiler (was Re: Fix In-Reply-To: <19980527225647.36082@follo.net> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep, being able to use NULL casted to void * is part of the C standard. Brian Feldman > On Wed, May 27, 1998 at 10:04:11PM +0200, Robert Nordier wrote: > > You may need -ltdf during linking. > > What does this contain? > > Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > inertia) in using this as our main compiler: The use of asm() for some > macros in the kernel, and the use of linker sets. What do you think > our chance of working around these are? > > > There is currently an unresolved bug in i386 long long support: avoid > > casting to long long. > > There is also what looks like a bug in handling of NULL - it doesn't > allow the use of ((void *)0) as NULL for function pointers. > > I may remember the C standard incorrectly (I haven't looked it up), > but I think it is required to. > > Eivind. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message