From owner-freebsd-current Tue Jun 2 18:07:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19772 for freebsd-current-outgoing; Tue, 2 Jun 1998 18:07:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19680 for ; Tue, 2 Jun 1998 18:06:58 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-120.camalott.com [208.229.74.120] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id UAA28607; Tue, 2 Jun 1998 20:05:14 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA02058; Fri, 29 May 1998 22:12:28 -0500 (CDT) (envelope-from joelh) Date: Fri, 29 May 1998 22:12:28 -0500 (CDT) Message-Id: <199805300312.WAA02058@detlev.UUCP> To: tlambert@primenet.com CC: eivind@yes.no, rnordier@nordier.com, current@FreeBSD.ORG In-reply-to: <199805292120.OAA14978@usr04.primenet.com> (message from Terry Lambert on Fri, 29 May 1998 21:20:43 +0000 (GMT)) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805292120.OAA14978@usr04.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> * Possibilities for exploiting the cross-CPU nature of XANDF >> How are XANDF's cross-cpu capabilities more powerful than gcc's? > You can distribute "binaries" and localize them to an architecture at > install time. > This means you can distribute commercial code that will run on x86, > Alpha, MIPS, PPC, 68k, VAX, SPARC, etc., etc.. Does it have problems with endianness, et al? That is, if a program, at compile time, needs to know its endianness (or another architecture-dependant detail), does it still work? > For FreeBSD, this means one "ports" CDROM will work for all future > architectures. I'll consider that an advantage when I see more architectures. > It also means that one "ports" CDROM will work for FreeBSD 3.x and > FreeBSD 235.x. A case of Bushmill's goes to the first person who shows me a port that bitrot doesn't kill before FreeBSD 235. (Memo to myself: add this to my will...) >>> * Better error checking/control >> How do you mean? > Full mapping of the error checking and warning space. GCC only maps > the parts that they thought were important, and then it's done pretty > haphazardly. Mapping, you mean, to diagnostics? -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message