Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!fluke!ssc-vax!bcsaic!paula From: paula@bcsaic.UUCP (Paul Allen) Newsgroups: comp.os.minix Subject: Re: GNU cc, etc. Message-ID: <14092@bcsaic.UUCP> Date: 16 Aug 89 18:48:46 GMT References: <21712@louie.udel.EDU> Reply-To: paula@bcsaic.UUCP (Paul Allen) Organization: Boeing Computer Services AI Center, Seattle Lines: 23 In article <21712@louie.udel.EDU> lcc!dana@seas.ucla.edu writes: + + Though I haven't looked at it myself yet, an associate of mine recently +compiled gcc, once with another compiler, another time with gcc (the +self-compiling bootstrap). He sez gcc doesn't use temporary files. It uses +gobs of virtual memory. + + Keep this in mind - a 386 Minix supporting this compiler will have to +provide useful virtual memory. A long time ago, I recompiled gcc with itself on a Sun while watching the size of the processes with the top program. As I recall, the cc1 process grew to just under a megabyte. Assuming the existence of a version of Minix that could support processes that big, I think you could get by with just a couple megabytes of extended memory. Of course, getting past that initial assumption is non-trivial! Paul Allen -- ------------------------------------------------------------------------ Paul L. Allen | pallen@atc.boeing.com Boeing Advanced Technology Center | ...!uw-beaver!bcsaic!pallen