public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bryce@waitaki.otago.ac.nz
To: gcc-gnats@gcc.gnu.org
Subject: java/5088: Can't create a java.lang.Object from CNI
Date: Tue, 11 Dec 2001 22:46:00 -0000	[thread overview]
Message-ID: <20011212064036.30713.qmail@sources.redhat.com> (raw)


>Number:         5088
>Category:       java
>Synopsis:       Can't create a java.lang.Object from CNI
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 11 22:46:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Bryce
>Release:        gcc version 3.1 20011207 (experimental)
>Organization:
>Environment:

>Description:
The test case below does not link.

$ gcc InvokeCNI.cc -lgcj
/tmp/ccoD0wXw.o: In function `main':
/tmp/ccoD0wXw.o(.text+0x48): undefined reference to `java::lang::Object::Object()'
collect2: ld returned 1 exit status

$ nm InvokeCNI.o | grep ObjectC 
         U _ZN4java4lang6ObjectC1Ev

$ nm ~/cvs/gcc/build/i686-pc-linux-gnu/libjava/java/lang/Object.o | grep ObjectC
00000030 T _ZN4java4lang6ObjectC2Ev

According to the C++ ABI spec:

<ctor-dtor-name> ::= C1	# complete object (in-charge) constructor
		   ::= C2	# base object (not-in-charge) constructor

>How-To-Repeat:
#include <gcj/cni.h>
#include <java/lang/Object.h>

int main(int argc, char *argv)
{
  using namespace java::lang;
  
  _Jv_CreateJavaVM (NULL);
  _Jv_AttachCurrentThread (NULL, NULL);
  
  new java::lang::Object ();
}

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-12-12  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 22:46 bryce [this message]
2001-12-15 16:46 Tom Tromey
2001-12-16 14:25 tromey
2001-12-16 14:54 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=20011212064036.30713.qmail@sources.redhat.com \
    --to=bryce@waitaki.otago.ac.nz \
    --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: 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).