So far it has been taking 2 hours to compile sql_yacc.cc from mysql3.22.
I had to find an old disk for swap, and it's swapping all the time.
top shows 156M size and 46M res., run time 20min's for cc1plus.
That probably means it's been waiting for swapping in 1h40m...
The box is a 333MHz PII, wi
In the last episode (Jan 01), Leif Neland said:
> So far it has been taking 2 hours to compile sql_yacc.cc from
> mysql3.22.
>
> I had to find an old disk for swap, and it's swapping all the time.
>
> top shows 156M size and 46M res., run time 20min's for cc1plus. That
> probably means it's been
[ moved to freebsd-ports ]
On 01-Jan-00 Leif Neland wrote:
> So far it has been taking 2 hours to compile sql_yacc.cc from mysql3.22.
This is an indication that something is SERIOUSLY wrong! MySQL has never taken
my PII-450 w/ 128MB RAM more than, say, 10-15 minutes to build/install.
It would b
> 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
> "Leif" == Leif Neland <[EMAIL PROTECTED]> writes:
>> 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 c
On Sat, Jan 01, 2000 at 01:32:19PM -0600, Dan Nelson wrote:
> > The box is a 333MHz PII, with 64M ram. Do I just need more ram to be
> > able to compile in reasonable time, or is something broken?
>
> You probably need more RAM. sql_yacc.cc is one of those "worst-case"
> programs as far as gcc i
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 04-Jan-00 Sasha Pachev wrote:
> 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.
Especially since different u
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
> > > th
> > 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 pro
On Sat, 1 Jan 2000, Dan Nelson wrote:
> In the last episode (Jan 01), Leif Neland said:
> > So far it has been taking 2 hours to compile sql_yacc.cc from
> > mysql3.22.
> >
> > I had to find an old disk for swap, and it's swapping all the time.
> >
> > top shows 156M size and 46M res., run ti
11 matches
Mail list logo