This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)

From: "B. Kosnik" <bkoz at nabi dot net>
To: Jerry Quinn <jlquinn at optonline dot net>
Cc: carlo at alinoe dot com, libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Mon, 28 Apr 2003 23:16:06 -0500
Subject: Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
References: <E190xa9-0006B0-00@tiamat><20030403103008.GA28026@alinoe.com><16012.17149.823856.404456@gargle.gargle.HOWL><20030411102928.GA32143@alinoe.com><16031.32556.123697.603768@gargle.gargle.HOWL><20030427153915.GA5850@alinoe.com><16044.51345.781643.861197@gargle.gargle.HOWL>

Jerry, I'm taking this as your white flag.

>In addition, there are strings in the cache.  How do these avoid
>allocating?  There is also another issue flagged by valgrind, but I
>don't know what it is from:

This is the internal string memory managment. You'll need to use an
allocator in your strings that is pre-allocated, or not use strings.

-benjamin

Follow-Ups:
- Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
  - From: Jerry Quinn

References:
- [v3] Fix PR libstdc++/10276
  - From: Jerry Quinn
- Re: [v3] Fix PR libstdc++/10276
  - From: Carlo Wood
- zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
  - From: Jerry Quinn
- Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
  - From: Carlo Wood
- Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
  - From: Jerry Quinn
- Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
  - From: Carlo Wood
- Re: zero-alloc cache (was Re: [v3] Fix PR libstdc++/10276)
  - From: Jerry Quinn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]