3.4 memory/compile time performance patches, round 2
Jan Hubicka
jh@suse.cz
Sat Feb 21 13:45:00 GMT 2004
> > Jan Hubicka wrote:
> >
> > >Mark,
> > >I would like to get more of memory patches to 3.4 branch.
> > >
> > I'm getting to the point where I'm not going to want any more such
> > patches. We're about a month out at this point, and yes,
> > memory/compile-time is a major issue, but it's also the kind of thing
> > where you can introduce weird failures that only occur on some systems,
> > and we don't want. that. So, this is a heads-up: in another week okr
> > so, I'm probably not going to accept any more of these patches for
> > 3.4.0. We can consider putting them in 3.4.1 if they've been proven on
> > the mainline by that point.
>
> This is fine for me. I don't think I have any other patches in mainline
> that makes really a lot of difference (but I will check and send mail
> shortly if I missed something). Some of them are waiting, but putting
It looks like everything important is merged. Mainline now produces
30MB of garbage compiling combine.i, while 3.4 branch 31MB.
15% of that memory can be saved by quite trivial patch:
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02072.html
That has not been reviewed for mainline yet tought.
Honza
More information about the Gcc-patches
mailing list