🚀 go-pugleaf

What are the known incompatibilities between .o files created with acc
and those created with gcc 2.0 (if any). That is, is it safe to link
with libraries generated by the two compilers? If not, what 
C constructs would cause problems? Do any well-known acc-compiled
libraries cause problems when linked with your gcc-compiled code?

We have reasons for wanting to mix both Sun and Gnu compiled code. For
example, with gcc,  we can compile with both -g and -O. acc won't
allow us to do this. On the other hand, Purify only works with acc.
Though I've been arguing for using only one family of compilers
(particularly because C++ is now in the equation), I can't seem to
convince the people on my project that this would simplify our lives. 
Now I'm wondering if my fears are unfounded.

I know that gdb chokes on acc-compiled code. Are there any issues with
respect to the way gcc does register allocation?  Any other gotchas? 

mark
--
fmrco!msommer@uunet.uu.net