public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@redhat.com To: gcc-gnats@gcc.gnu.org Subject: libgcj/5103: jni.h sets java-exceptions Date: Thu, 13 Dec 2001 09:06:00 -0000 [thread overview] Message-ID: <20011213170210.12385.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2001-12-13 17:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-13 9:06 tromey [this message] 2001-12-16 14:43 tromey
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=20011213170210.12385.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --cc=gcc-gnats@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: linkBe 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).