From: "Boehm, Hans" <hans.boehm@hp.com>
To: Bryce McKinlay <bmckinlay@gmail.com>,
Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: GCC Java <java@gcc.gnu.org>
Subject: RE: Two quick GC questions [was Re: [REVIVED: PATCH PR42811,4.5 regression] java.lang.ExceptionInInitializerError in ecj1]
Date: Fri, 19 Feb 2010 03:22:00 -0000 [thread overview]
Message-ID: <238A96A773B3934685A7269CC8A8D0425784FAA8EC@GVW0436EXB.americas.hpqcorp.net> (raw)
In-Reply-To: <7230133d1002181413h5c6abcf8ge7a989349e0fa3c0@mail.gmail.com>
> From: Bryce McKinlay
>
> In theory, there could also be a performance advantage to
> having a single library because a smart linker / linker
> script could optimize internal calls to things like
> GC_malloc, speeding up the allocation path by avoiding PLT
> indirection.
>
> Bryce
>
Also in theory, in this case, you should be able to have your cake and eat it, too. The idea was that we should be able to inline the fast path that looks only at a small collection of the thread-local free-lists, but then calls into the GC library on the slow path. GC7.x generally has the infratsructure for that. But it's not clear anyone has the time to do this. Last time I looked into this, the current gcj allocation path is still much slower than one would like, so this should help.
Hans
next prev parent reply other threads:[~2010-02-19 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B6C9B26.3010106@gmail.com>
[not found] ` <4B6D0C67.5030500@gmail.com>
2010-02-14 22:23 ` JVMTI events system and _jvmtiEnvironments uninitialised memory problem? [was Re: [PATCH " Dave Korn
[not found] ` <4B78BA6D.5000603@gmail.com>
[not found] ` <7230133d1002150504r23738e28if92303426c349661@mail.gmail.com>
[not found] ` <4B7CC61E.1050709@gmail.com>
[not found] ` <4B7D631B.8030401@gmail.com>
2010-02-18 20:41 ` Two quick GC questions [was Re: [REVIVED: PATCH " Dave Korn
2010-02-18 22:06 ` Boehm, Hans
2010-02-19 7:04 ` Dave Korn
2010-02-18 22:13 ` Bryce McKinlay
2010-02-19 3:22 ` Boehm, Hans [this message]
2010-02-20 18:22 ` Dave Korn
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=238A96A773B3934685A7269CC8A8D0425784FAA8EC@GVW0436EXB.americas.hpqcorp.net \
--to=hans.boehm@hp.com \
--cc=bmckinlay@gmail.com \
--cc=dave.korn.cygwin@googlemail.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).