From: Anthony Green <green@cygnus.com>
To: "'khendricks@ivey.uwo.ca'" <khendricks@ivey.uwo.ca>
Cc: "'linuxppc-dev@lists.linuxppc.org'" <linuxppc-dev@lists.linuxppc.org>
Subject: Kaffe from cvs and some patches
Date: Sun, 30 Jul 2000 13:40:20 -0700 [thread overview]
Message-ID: <01BFFA2B.F8827460.green@cygnus.com> (raw)
Kevin wrote:
> I built kaffe cvs using the cvs version of libffi and basicly it compiles
but
> does not really run any truly multi-threadsed apps
> (see test/regressions/ThreadLocalTest.java for instance).
libffi itself is thread safe. I suspect that Kaffe is using it incorrectly.
Do you (or anyone else) know what the problem is?
AG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-30 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 20:40 Anthony Green [this message]
2000-07-30 22:54 ` Kaffe from cvs and some patches hendricks
-- strict thread matches above, loose matches on Subject: below --
2000-07-24 12:44 Hendricks, Kevin
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=01BFFA2B.F8827460.green@cygnus.com \
--to=green@cygnus.com \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).