This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Patch: FYI: javah, volatile, and CNI
- From: Tom Tromey <tromey at redhat dot com>
- To: David Daney <ddaney at avtrex dot com>
- Cc: GCJ-patches <java-patches at gcc dot gnu dot org>
- Date: 29 Jan 2007 08:22:59 -0700
- Subject: Re: Patch: FYI: javah, volatile, and CNI
- References: <m37iv9bj97.fsf@localhost.localdomain> <45BD9263.4010506@avtrex.com>
- Reply-to: tromey at redhat dot com
>>>>> "David" == David Daney <ddaney@avtrex.com> writes:
>> This fixes the 'volatile' problem that Andrew pointed out.
>> I just put this in Classpath, the libjava change also updates the .h
>> files.
David> Perhaps, but I am getting these unexpected changes from 'svn st' with
David> a java-maintainer-mode build:
The files look ok to me. I just updated, 'svn status' claims I have
no diffs, and I spot-checked a file:
opsy. grep volatile java/lang/SecurityManager.h
static ::java::lang::SecurityManager * volatile current;
So ... did you rebuild using the latest gjavah, i.e., the one in svn?
I have my build set up to use the gjavah classes in $srcdir via a
bootstrap JVM. That way gjavah changes are immediately put into use.
Tom