linux, compilers and paging

Previous thread: No subject found in mail header by proven on Friday, November 15, 1991 - 12:40 pm. (1 message)

Next thread: Important! Bug in /usr/include/ctypes.h by Theodore Ts'o on Friday, November 15, 1991 - 7:42 pm. (1 message)
To: <linux-activists@...>
Date: Friday, November 15, 1991 - 5:11 pm

One of the things I find anoying about minix is having multiple compilers
(just bcc and gcc). Just using one compiler (gcc in linux) really helps
adhere to the KISS principle. But as Robert Blum points out, gcc is
a hog. I guess this is why we see the 1.7 Meg buffer caches.

While paging might be nice, you still have to reload gcc N times to compile
an N module program, for the typical makefile. The only other way I see
around the huge buffer cache is to implement the sticky bit to keep a
programs pages in memory.

The other alternative, #ifdef GCC, #ifdef C386 etc throughout the code, and
having multiple object file types about, is even less savory. I would
rather live with setting and clearing sticky bits before and after heavy
compile sessions. I wonder what others think though?

Previous thread: No subject found in mail header by proven on Friday, November 15, 1991 - 12:40 pm. (1 message)

Next thread: Important! Bug in /usr/include/ctypes.h by Theodore Ts'o on Friday, November 15, 1991 - 7:42 pm. (1 message)