I was compiling an X program called xpaint the other day when I
ran into some (to me) inexplicable behaviour. Every thing was going ok
until gcc started to compile tif_fax3.c. It got stuck on this one for a
long time and I couldn't do anything else on the system. I tried it in
X and I couldn't move the mouse or bring up other windows. I tried it in
character mode and I couldn't login on another vc.
I then tried to find out what is causing this behaviour. It was
that tif_fax3.c includes a huge include file (~400k) that contains an
intialized matrix (). Well, I'm surprised because:
- Why should gcc spend so much time processing the matrix (half
an hour before I killed it). Obviously it is doing some kind of
optimization but what?
- Whatever gcc is up to, I expect a preemptive multi-tasking system
to allow me to do other things while gcc is chugging along.
My system is a 486 sx/25 clone with 16mb RAM, using linux99pl10
and gcc 2.3.3.
Any enlightening comments will be appreciated.