platt@emory.uucp (Dan Platt) (11/24/87)
In article <3606@uwmcsd1.UUCP> cmaag@csd4.milw.wisc.edu.UUCP (Christopher N Maag) writes: >In article <312@apex.UUCP> gary@apex.UUCP (Gary Wisniewski) writes: >>[...] >>Strange happenings: >> I got an internal compiler [error] from "emit.c" when it hit the line: >> qtraverse[qmac[qx]++]; >I've also gotten an "internal compiler error" with a similar (although >a little more complicated) expression: > /* add the new packet to the input queue */ > imp_list[i].in_queue[imp_list[i].in_q_ptr++]=wrk_packet; >I was running QuickC at the time. Needless to say, this runs fine under >MSC v. 4.0, Mark William's C, and Berkeley UNIX C. When I was trying to >isolate the problem so I could submit it to Microsoft I cut the program >from about 500 lines down to 50, and, you guessed it, the problem went >away. > >Has anyone brought this problem to Microsoft's attention yet? I would have, >but I'm a little short on time right now. > >Chris. Actually, I've had problems like this since version 4.0 only when I used microsoft make. It seemed that when I compiled larger programs with make, I'd get 'internal compiler error's. These wouldn't be present if I used msc or cl directly -- only when I compiled them through make. I was able to correct some of this problem (at least to make it usable for most tasks --- but not all) by running 'exemod make.exe /max 300' allowing 300(hex) paragraphs maximum available to make. I assume that there may be an incompatibility with their 'malloc()' (or what ever the compiler is using) when a spawn()'ed process is using that on my system. (I can't think of any other explanation... any other ideas out there?) That is also a little wierd since I have an almost standard ibm pc (real big blue) with a st225 (waiting for disaster), a quadram with 384k (for a total of 640k ... plenty according to msoft), and a video-7 vega deluxe (ega + higher res available). There's nothing there that I can see that would cause a problem.... Anyway, when I get C5.0 and quickC, I found that I was getting all sorts of 'internal compiler error's. Not only that, but QuickC hung my system on almost all compiles (though the command line version didn't). All in all, on my system, I've found C ver 5.0 completely unusable (I can't compile a thing with it!!!). If anyone has any other comments on this, or similar experiences (hung systems and such on a "real" ibm), I'd appreciate hearing about it. Thanks in advance, Dan Platt