Orca/C 2.0 problems

[mills@MAX.EE.LSU.EDU (John Mills)]

I've been working with Orca's latest C compiler since it finally arrived
the other week. Have any of you guys had the following problems...
  o no distinction between stdout & stderr. In order to print a list
    of errors, all output must be printed.

  o compiler does not save any functions after the first one with
    an error (even if they are good ones - ie. no errors). No ~GLOBALS
    are saved either. 
    To test this problem, try playing with the following code. Move the
    bad function around to different places in the file, compile, then 
    do a dumpobj (I used dumpobj -x -o). It'll show that only those
    functions processed BEFORE the bad one are actually saved.
 
=============================== cut here ==================================
#pragma noroot
 
test2 (void)
{ /* this is OK */
}
 
test1 (void)
{
    this is an error;
}

test3 (void)
{ /* ok too */
}