Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Jun 1998 10:15:52 +0200
From:      Eivind Eklund <eivind@yes.no>
To:        joelh@gnu.org, tlambert@primenet.com
Cc:        rnordier@nordier.com, current@FreeBSD.ORG
Subject:   Re: Fix for undefined "__error" and discussion of shared object versioning
Message-ID:  <19980603101552.35895@follo.net>
In-Reply-To: <199805300312.WAA02058@detlev.UUCP>; from Joel Ray Holveck on Fri, May 29, 1998 at 10:12:28PM -0500
References:  <199805292120.OAA14978@usr04.primenet.com> <199805300312.WAA02058@detlev.UUCP>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 29, 1998 at 10:12:28PM -0500, Joel Ray Holveck wrote:
> >>> * 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?

Yes.  You use if() instead of #ifdef, and TenDRA do dead code
elmination at install time.


BTW: I just found out that TenDRA _do_ support __asm().  This is
supported to a limited degree in the C frontend (it can only send a
pure string to the backend, which will typically insert it in the asm
output).  I'm not certain if this is enough for our needs.

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

Yes.

Another neat part of this is that TenDRA indicate what you're in
violation of by ISO section - always nice when you have to hit some
Linuxer over the head with his violation ;-)

Eivind.

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?19980603101552.35895>