Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 May 1998 22:12:28 -0500 (CDT)
From:      Joel Ray Holveck <joelh@gnu.org>
To:        tlambert@primenet.com
Cc:        eivind@yes.no, rnordier@nordier.com, current@FreeBSD.ORG
Subject:   Re: Fix for undefined "__error" and discussion of shared object versioning
Message-ID:  <199805300312.WAA02058@detlev.UUCP>
In-Reply-To: <199805292120.OAA14978@usr04.primenet.com> (message from Terry Lambert on Fri, 29 May 1998 21:20:43 %2B0000 (GMT))
References:   <199805292120.OAA14978@usr04.primenet.com>

next in thread | previous in thread | raw e-mail | index | archive | help

>>> * 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805300312.WAA02058>