🚀 go-pugleaf

In article <1992May19.205623.1@tesla.njit.edu>, erh0362@tesla.njit.edu (Elliotte Rusty Harold) writes:
|> 
|> 	How well does code compiled with gcc 2.1 integrate with code 
|> compiled with the bundled cc on a SPARC? I've got a heavily 
|> mathematical program split across four source files. If I compile all 
|> four source files with either cc or gcc, the program runs fine and 
|> gives correct results for a case I'm able to check analytically. I'd 
|> like to compile three of the pieces with gcc because in general its 
|> faster and allows me to use ANSI standard code and one with cc to take 
|> advantage of the -fsingle flag that doesn't seem to have a gcc 
|> equivalent. However the code created by the hybrid objects produces 
|> erroneous results. Can I link together code produced by gcc with code 
|> from other compilers? If so do I need to do anything more than "gcc 
|> file1.o file2.o file3.o file4.o -lm"? Will this work if I get the gnu 
|> linker? If I can't link gcc code produced by the bundled cc compiler, 
|> can I link with code produced by f77? I'm using a Sparc II running 
|> SunOS 4.1.1.

This could be a problem with function return values, so try -fpcc-struct-return.
However if I remember correctly isn't -fsingle obsolete with ANSI C where floats
aren't promoted to doubles. My memory is a bit hazy here but I seem to recall there
being problems with prototypes in early ANSI C compilers.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm