🚀 go-pugleaf

The recent discussion regarding gcc 2.4.0's floating point return conventions,
(with respect to sun3 and returning only in 68881 fp0, rather than also in
d0/d1), has lead me to wish for a "pure gnu" 680x0 configuration, that has the
following characteristics:

Code compiled with it, need only work with other .o and libs compiled with it,
(i.e. no outside conventions need be followed. No need to link with sun
compiled libs).

It may REQUIRE the use of gas and gnu ld, and be debuggable only by gdb.

It uses the most optimal (for itself), call and return and register
conventions. If it works best to pass 3 args in d0/1/2, and returns in d0 or
fp0 only, (or maybe even a0 for pointer returns), then use that convention. If
it works best to use all 8 regs as scratch, or only 1, then do it that way.

What I want is the best possible code produced by a cross compiler for embedded
systems, without constraint of matching some vendor's conventions.

So, has anyone ever played around with a range of conventions, to find out
what works best overall?

Is anyone else out there interested in such a configuration? I assume that
most people doing cross compilers are not actually targeting full blown unix
systems. I mean why bother cross compiling from a sun4 to a sun3. Just run on
a sun3.

Isn't anyone else out there crossing to embedded systems, where anything goes
as far as the compiler conventions?

Any ideas or suggestions are welcome. Even a compendium of the existing 680x0
configurations for gcc would be nice. Anyone already have this done?

	-Don
	derway@ndc.com

Newsgroups: gnu.gcc.help
Subject: Vanilla 680x0 gcc configuration
Summary: 
Expires: 
Sender: 
Followup-To: 
Distribution: gnu
Organization: California Institute of Technology, Pasadena
Keywords: