From: Andrew Haley <aph@redhat.com>
To: abhishek desai <abhi00@gmail.com>
Cc: java@gcc.gnu.org
Subject: Re: Using libgcj with different memory management library.
Date: Mon, 08 Jun 2009 09:45:00 -0000 [thread overview]
Message-ID: <4A2CDDB2.3060206@redhat.com> (raw)
In-Reply-To: <898285d30906080243o70b109a0g54a6b3b00a87f4d2@mail.gmail.com>
abhishek desai wrote:
>> I don't understand how this can work. The gc is a memory manager; how
>> can it use some other memory manager to do its own work? You'll have
>> to explain a little more.
>
> From what I understand GC uses GC_unix_get_mem to allocate memory
> which calls mmap on /dev/zero on my system. This memory is managed by
> GC for object allocation and also for GC internal working. I hope this
> is correct. What I want to do is replace the mmap with my_malloc call
> which will return a pointer to the allocated memory. my_malloc will
> allocate memory from an internal fixed memory pool.
That will work fine.
Andrew.
prev parent reply other threads:[~2009-06-08 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 7:06 abhishek desai
2009-06-08 9:09 ` Andrew Haley
2009-06-08 9:43 ` abhishek desai
2009-06-08 9:45 ` Andrew Haley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2CDDB2.3060206@redhat.com \
--to=aph@redhat.com \
--cc=abhi00@gmail.com \
--cc=java@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).