This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Speeding up ggc-simple on stage1
- To: Zack Weinberg <zack at wolery dot cumb dot org>
- Subject: Re: Speeding up ggc-simple on stage1
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sat, 15 Jan 2000 18:53:50 -0700
- cc: Mark Mitchell <mark at codesourcery dot com>, oliva at lsd dot ic dot unicamp dot br, gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <20000115173202.C8447@wolery.cumb.org>you write:
> On Sat, Jan 15, 2000 at 05:20:10PM -0800, Mark Mitchell wrote:
> > >>>>> "Alexandre" == Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:
> > >> I'm all for speeding up the compiler -- but I'm old-fashioned.
> > >> Let's profile first, and attack the hot spots!
> >
> > Alexandre> But attacking the hot spots is precisely what I'm
> > Alexandre> doing. ggc-simple seems to be just too slow.
> >
> > Fair enough. I think you're right -- the best thing to do is find a
> > way to get page-aligned memory even if doing so is something of a
> > nuisance. I'm not sure what scheme is best for the system you're on.
>
> Might it work to call sbrk() directly?
If I remember correctly, programs that use malloc should not be calling
sbrk directly.
jeff