From: hendricks <kevin.hendricks@sympatico.ca>
To: "green@cygnus.com" <green@cygnus.com>
Cc: "'khendricks@ivey.uwo.ca'" <khendricks@ivey.uwo.ca>,
"'linuxppc-dev@lists.linuxppc.org'"
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Kaffe from cvs and some patches
Date: Sun, 30 Jul 2000 18:54:59 -0400 [thread overview]
Message-ID: <3984B243.AC88BF64@sympatico.ca> (raw)
In-Reply-To: 01BFFA2B.F8827460.green@cygnus.com
Hi Anthony,
If you are interested in kaffe, Godmar committed my changes and it
should build just fine under cvs.
I also built it using unix-pthreads (native linuxthreads) and it also
seems to work well (with a few minor build modifications).
As for libffi,I was using the cvs version 2.X. As for threadsafety, I
am not sure that is the issue at all.
Given the sysdepCallMethod now exists for ppc, it should improve
performance over libffi (simply less overhead) (if you can get libffi to
work).
Try a cvs checkout of kaffe, it should build and work with both
unix-jthreads and unix-pthreads.
Kevin
Anthony Green wrote:
>
> 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
--
--
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
Richard Ivey School of Business, University of Western Ontario
London, Ontario N6A-3K7 CANADA
khendricks@ivey.uwo.ca, (519) 661-3874, fax: 519-661-3959
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-30 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 20:40 Kaffe from cvs and some patches Anthony Green
2000-07-30 22:54 ` hendricks [this message]
-- 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=3984B243.AC88BF64@sympatico.ca \
--to=kevin.hendricks@sympatico.ca \
--cc=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).