public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Craig Vanderborgh <craigvanderborgh@gmail.com>
To: java@gcc.gnu.org
Subject: gnu.gcj.RawData vs. long
Date: Mon, 18 Jul 2011 16:08:00 -0000	[thread overview]
Message-ID: <CAG6o7Q8jwb1_UuGMorjPUinOnwObX9mPFL0MfJ=taLHEFkRiQg@mail.gmail.com> (raw)

Hello all:

I am working to make some of our code more portable.  We "gcj-ified"
our source several years back, including making liberal use of
gnu.gcj.RawData * class members to store pointers for native (CNI)
code within object instances.

The problem is that gnu.gcj.RawData * is not portable.  The question
is: can I use "long" for the type instead without garbage collection
problems?  Can my native code store the pointer value in a Java "long"
in the CNI with impunity, or will Boehm GC think these pointers needs
to be considered for collection?

Please advise.

Thanks in advance,
Craig Vanderborgh
Voxware Incorporated

             reply	other threads:[~2011-07-18 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 16:08 Craig Vanderborgh [this message]
2011-07-18 16:18 ` Bryce McKinlay

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='CAG6o7Q8jwb1_UuGMorjPUinOnwObX9mPFL0MfJ=taLHEFkRiQg@mail.gmail.com' \
    --to=craigvanderborgh@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).