From owner-freebsd-platforms Fri Aug 18 14:47:44 2000 Delivered-To: freebsd-platforms@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 3B2CB37B422 for ; Fri, 18 Aug 2000 14:47:37 -0700 (PDT) Received: (qmail 23313 invoked from network); 18 Aug 2000 21:47:31 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 18 Aug 2000 21:47:31 -0000 Date: Sat, 19 Aug 2000 07:47:26 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Bruno BEC Cc: freebsd-platforms@FreeBSD.ORG Subject: Re: compile FreeBSD with ANSI compiler In-Reply-To: <399D02FC.BEAC8D98@capgemini.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-platforms@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 18 Aug 2000, Bruno BEC wrote: > Hi all, > > In order to have better performances on a new platform we intend to > compile FreeBSD with a specific ANSI-C compliant compiler instead of > gcc. > We made the same experience with the Linux Kernel and had bad surprises > due to significant non ANSI code souce (this code is not rejected by gcc > > which is not fully ANSI-C). > > Did one of you have any experience or information about the ANSI > compliance of the FreeBSD kernel ? It is similar to Linux -- very non-conformant. Last November, compiling LINT with 'gcc -pedantic -ansi ...' gave 14064 lines of warnings after removal of 50000 (?) lines of duplicated warnings for machine-generated code in . That's with gcc'isms like __inline and __attribute__((__packed__) (ick) accepted without warnings. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-platforms" in the body of the message