This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
libgcj/5103: jni.h sets java-exceptions
- From: tromey at redhat dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 13 Dec 2001 17:02:10 -0000
- Subject: libgcj/5103: jni.h sets java-exceptions
- Reply-to: tromey at redhat dot com
>Number: 5103
>Category: libgcj
>Synopsis: jni.h sets java-exceptions
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Dec 13 09:06:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Tom Tromey <tromey@redhat.com>
>Release: current cvs
>Organization:
>Environment:
>Description:
Right now our jni.h includes javaprims.h,
which has this line:
#pragma GCC java_exceptions
This is bad if the user is trying to compile
ordinary (non-CNI) C++ code.
The fix here is to write jni.h in a way that doesn't
assume you're using gcj.
If we assume gcc we can still use the __mode__ extension
for typedefs. Or, if we assume inttypes.h we can use another
method. Failing that we'd have to introduce a platform-specific header.
We'll also need a "gcj-compatible" mode so that the
typedefs are omitted. That will let us continue to include our jni.h
in jni.cc.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: