[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: Memory usage when opening Linux Kernel in KDevelop
From:       Milian Wolff <mail () milianw ! de>
Date:       2010-11-22 12:09:03
Message-ID: 201011221309.03583.mail () milianw ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 21 November 2010 20:03:53 Christoph Bartoschek wrote:
> Am Sonntag 21 November 2010 schrieb Christoph Cullmann:
> > On Sunday 21 November 2010 00:02:13 Milian Wolff wrote:
> > >   On Saturday 20 November 2010 23:33:57 David Nolden wrote:
> > > > I don't remember anything about rxx::allocator, i guess its just the
> > > > default for C++.
> > > 
> > > For the cpplang plugin? But the question is *why*, really - to me it
> > > looks like one of Robertos "I write my own allocator" - "Why?" -
> > > "Because I can!"  moments... I'll send him a mail asking him for the
> > > reasons.
> 
> Does it store the size of the allocated chunks? It is better to not store
> it. This can save some memory.

You'll have to study the sources for yourself.

And I've got a reply from Roberto, the allocator is used in the mem pool for 
the AST among other things, so it's perfectly fine (compare to e.g. kdev-pg-
allocator.h).

Bye
-- 
Milian Wolff
mail@milianw.de
http://milianw.de

["signature.asc" (application/pgp-signature)]

-- 
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


[prev in list] [next in list] [prev in thread] [next in thread]