Bug list for Microsoft C

[Eric Johnson]

[...]

In article <372 at scolex>, seanf at sco.COM (Sean Fagan) writes:
> In article <4516 at pasteur.Berkeley.Edu> iverson at cory.Berkeley.EDU.UUCP (Tim Iverson) writes:
> >int i=1, j=33;
> >
> >main() {
> >    printf("%x\n", 1<<33);
> >    printf("%x\n", 1>>33);
> >    printf("%x\n", i<<j);
> >    printf("%x\n", i>>j);
> >}
> >What results do you get? (This might even be interesting on non 86 machines;
> >oh boy, I just checked a non 86, and it failed too.)
> 
> >Mike Stump, Cal State Univ, Northridge Comp Sci Department
> >aeusemrs at csuna.csun.edu
> 
> ----------------
> Sean Eric Fagan
> seanf at sco

My results:
HP-UX [1]           MS-DOS [2]
  0                   0
  0                   0
  0                   2
  0                   0
[1] Hewlett-Packard 320 workstation, running HP-UX 5.5.
[2] Microsoft C 4.0, DOS 3.1.

What are the correct results? (I assume MSC is wrong, but I'm not sure
about the HP).

And anyway, back to the original purpose of the posting:
could someone email me, or post, a copy of the MSC bug list?
I'm interested to know what to expect from the compiler. I've already
come across what I think are bugs, especially in the malloc/free
routines (I seem to lose RAM as the program runs), but it would
be nice to know I'm not the only one hitting those problems.

Thanks,
-Eric


-- 
Eric F. Johnson          | Phone +1 612-894-0313             | Are we
Prime Automation,Inc     | UUCP: bungia!pai!erc              | having
12201 Wood Lake Drive    | UUCP: sun!tundra!pai!erc          | fun
Burnsville, MN 55337 USA | BIX:  erc                         | yet?