On Mon, Jan 03, 2000 at 07:23:36PM -0700, Sasha Pachev wrote:
> Leif Neland wrote:
> >
> > > The reason for this is that some gcc optimizations stages takes
> > > exponentially more memory when compiling big functions.
> > > bison produces one big function for the grammar parsing and its
> > > this that takes a long time to compile; To compile sql_yacc.cc quickly
> > > on Intel, you nead at least 160M of free ram. On a PentiumII 400mz with 256M
> > > ram, it takes 11 seconds to compile sql_yacc.o. Having to use swap
> > > can easily make things 1000 times slower
> > >
> >
> > Is amount of ram available (portably) to configure?
> > So configure could decide to use --low-memory by itself? Allowing
> > overrides, naturally.
> >
> > Leif
> >
>
> There is actually a method to portably guess how much RAM your have available
> from configure -- just write a small C program that will keep malloc()-ing until
> it gets an error, but I do not think it is worth the effort.
There is also no guarantee that the allocated memory will be
available for real use (keyword resource overcommitting).
--
Regards,
Sascha Schumann
Consultant
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
