This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: gcc 3.x custom allocators

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Rob Savoye <rob at welcomehome dot org>
Cc: libstdc++ at gcc dot gnu dot org
Date: Fri, 10 Jan 2003 14:43:53 -0600
Subject: Re: gcc 3.x custom allocators
References: <20030109173544.A785@welcomehome.org><20030110121254.37dbb073.bkoz@redhat.com><20030110113830.B7899@welcomehome.org>

>  I don't see an attachement. :-)

Sorry. Here it is...

>  For sure. Putting data structures in shared memory is a pretty common
>real-time application trick. This was the first time I'd done this 100% in
>C++ though. I use this code to create a std::list in the shared memory that's
>a queue of messages between 2 tasks. What's libhoard ?

It's a different underlying allocator, some kind of optimized malloc.

www.hoard.org

-benjamin

Attachment: custom_alloc.cc
Description: Binary data

References:
- gcc 3.x custom allocators
  - From: Rob Savoye
- Re: gcc 3.x custom allocators
  - From: Benjamin Kosnik
- Re: gcc 3.x custom allocators
  - From: Rob Savoye

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