From owner-freebsd-current Wed Apr 7 23:17: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (c1-64-dbn.dial-up.net [196.34.155.64]) by hub.freebsd.org (Postfix) with ESMTP id BCFD8153BC for ; Wed, 7 Apr 1999 23:16:49 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id IAA26867; Thu, 8 Apr 1999 08:09:24 +0200 (SAT) From: Robert Nordier Message-Id: <199904080609.IAA26867@ceia.nordier.com> Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: from John Polstra at "Apr 7, 99 08:17:53 pm" To: jdp@polstra.com (John Polstra) Date: Thu, 8 Apr 1999 08:09:22 +0200 (SAT) Cc: bde@zeta.org.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Bruce Evans wrote: > > > Everything should be buildable with CC=aac (any ANSI compiler), but > > that's asking too much for programs like kernels and boot blocks. > > The problem in this case is just that the compilers require > different command line options. It's asking _way_ too much to > require those to be identical. The main issue with supporting both gcc and egcs -- at least beyond the next few weeks -- is really that they have different optimization characteristics. Space is sufficiently tight in boot2 that it's often been necessary to refer to the emitted code, and move C statements around, or do things like change ints to chars, just to get everything to fit. So supporting anything other than egcs is likely to become much more than a makefile problem. Also for reasons of space, internal boot2 functions in assembly language require use of a non-standard calling convention (the called functions pop argument from the stack), so ability to use some arbitrary ISO compiler can't be guaranteed on principle, and is fairly unlikely in practice. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message