From: Helge Hess <helge.hess@skyrix.com>
To: jeff.sturm@commerceone.com
Cc: "Boehm, Hans" <hans_boehm@hp.com>,
'Matthias Klose' <doko@cs.tu-berlin.de>,
gcc@gcc.gnu.org, java-discuss@sources.redhat.com,
ovidiu@cup.hp.com
Subject: Re: ObjC configured --with-objc-gc needs external Boehm gc
Date: Wed, 17 Jan 2001 11:56:00 -0000 [thread overview]
Message-ID: <3A65F8F0.794F6157@skyrix.com> (raw)
In-Reply-To: <3A65E8FA.9F10DACF@appnet.com>
Jeff Sturm wrote:
> Can you say much slowdown is due to the use of thread primitives in libobjc vs.
> how much is due to memory allocation? Using boehm-gc might even be beneficial
> to the threaded runtime... I've observed poor performance from the standard
> (thread-safe) allocator on some systems, including glibc.
No, unfortunatly I can't, I didn't make any memory timings (except with
mingw32, where the default allocator is *extremly* slow).
If this is of interest to you, one major problem with the (GNU) libobjc
is that all operations referring class objects by name are compiled to
hashtable lookups instead of static references, eg
[NSString alloc]
ends up int
objc_msg_send(objc_class_lookup("NSString"),@sel(alloc));
And this objc_class_lookup is protected by a mutex ...
best regards
Helge
--
SKYRIX Software AG http://www.skyrix.com/
next prev parent reply other threads:[~2001-01-17 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 16:22 Boehm, Hans
2001-01-16 17:24 ` Matthias Klose
2001-01-17 3:13 ` Helge Hess
2001-01-17 0:41 ` Ovidiu Predescu
2001-01-17 2:03 ` Fergus Henderson
2001-01-17 9:13 ` Tom Tromey
2001-01-17 3:17 ` Helge Hess
2001-01-17 10:49 ` Jeff Sturm
2001-01-17 11:56 ` Helge Hess [this message]
2001-01-17 10:44 ` Jeff Sturm
2001-01-17 11:22 ` Tom Tromey
2001-01-17 12:00 ` Helge Hess
-- strict thread matches above, loose matches on Subject: below --
2001-01-17 11:39 Boehm, Hans
2001-01-17 9:35 Boehm, Hans
2001-01-16 15:52 Boehm, Hans
2001-01-16 15:02 Boehm, Hans
2001-01-16 14:37 Boehm, Hans
2001-01-16 15:25 ` Matthias Klose
2001-01-16 16:02 ` Helge Hess
2001-01-16 14:11 Matthias Klose
2001-01-16 14:18 ` Ovidiu Predescu
2001-01-16 14:37 ` Tom Tromey
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=3A65F8F0.794F6157@skyrix.com \
--to=helge.hess@skyrix.com \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=hans_boehm@hp.com \
--cc=java-discuss@sources.redhat.com \
--cc=jeff.sturm@commerceone.com \
--cc=ovidiu@cup.hp.com \
/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).