From: Bryce McKinlay <bmckinlay@gmail.com>
To: Dave Korn <dave.korn.cygwin@gmail.com>
Cc: GCC Java <java@gcc.gnu.org>
Subject: Re: Usage of _Jv_AttachCurrentThread, _Jv_AttachCurrentThreadAsDaemon, _Jv_DetachCurrentThread.
Date: Wed, 10 Apr 2013 09:34:00 -0000 [thread overview]
Message-ID: <CALUNu-r6UBTZhwkOb4uqfrKg5uSnzccMLWAQQbW5xc4Fvwjccw@mail.gmail.com> (raw)
In-Reply-To: <51645BD5.3090906@gmail.com>
On Tue, Apr 9, 2013 at 7:20 PM, Dave Korn <dave.korn.cygwin@gmail.com> wrote:
> I could fix this by either adding a !defined(GC_WIN32_THREADS) in the same
> way as Solaris disables these functions, or I could add an implementation of
> the functions in boehm-gc for Cygwin, which is posixy and pthread-based.
As Andrew said, these are used by the JNI (& CNI) "invocation API",
which allows calling into Java code from a non-Java app.
It might be worth checking if newer versions of the GC already have
improvements here for Cygwin. libgcj's copy of boehm-gc is very old
and we really ought to update it!
> Also on the same topic, would there be any value added by providing Cygwin
> implementations of GC_suspend_thread, GC_resume_thread and
> GC_is_thread_suspended, which are called from _Jv_SuspendThread,
> _JV_ResumeThread, _JV_IsThreadSuspended in boehm.cc and currently #if'd out by
> a test on GC_WIN32_THREADS?
Well, I don't think anything in libgcj really uses these. They might
be useful as part of a debugging interface.
Bryce
next prev parent reply other threads:[~2013-04-10 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 18:17 Dave Korn
2013-04-10 8:24 ` Andrew Haley
2013-04-10 9:34 ` Bryce McKinlay [this message]
2013-04-10 23:18 ` Dave Korn
2013-04-11 5:03 ` Boehm, Hans
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=CALUNu-r6UBTZhwkOb4uqfrKg5uSnzccMLWAQQbW5xc4Fvwjccw@mail.gmail.com \
--to=bmckinlay@gmail.com \
--cc=dave.korn.cygwin@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).