public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "overholt at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/26138]  New: Lots of warnings with gcj .jar -> .so
Date: Mon, 06 Feb 2006 20:36:00 -0000	[thread overview]
Message-ID: <bug-26138-9773@http.gcc.gnu.org/bugzilla/> (raw)

When natively-compiling the Eclipse jars, I get lots of warnings similar to
this:

org/eclipse/swt/internal/SWTEventObject.java:0: warning:
'_otable_syms_org_eclipse_swt_internal_SWTEventObject' defined but not used
org/eclipse/swt/internal/SWTEventObject.java:0: warning:
'_itable_syms_org_eclipse_swt_internal_SWTEventObject' defined but not used

I am compiling this jar like this:

/usr/bin/gcj -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4
-fasynchronous-unwind-tables -fPIC -findirect-dispatch -fjni
/var/tmp/eclipse-3.1.2-1jpp_4fc-buildroot/usr/lib/gcj/eclipse/org.eclipse.swt.gtk.linux.x86_3.1.1.jar.1.jar
-o
/var/tmp/eclipse-3.1.2-1jpp_4fc-buildroot/usr/lib/gcj/eclipse/org.eclipse.swt.gtk.linux.x86_3.1.1.jar.1.jar.o

$ gcj --version
gcj (GCC) 4.1.0 20060131 (Red Hat 4.1.0-0.20)

i386


-- 
           Summary: Lots of warnings with gcj .jar -> .so
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: overholt at redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26138


             reply	other threads:[~2006-02-06 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 20:36 overholt at redhat dot com [this message]
2006-02-06 20:37 ` [Bug java/26138] " tromey at gcc dot gnu dot org
2006-02-06 20:59 ` pinskia at gcc dot gnu dot org
2006-02-06 21:05 ` tromey at gcc dot gnu dot org
2006-02-07 19:23 ` tromey at gcc dot gnu dot org
2006-03-15 20:19 ` tromey at gcc dot gnu dot org
2006-03-15 23:15 ` aph at gcc dot gnu dot org

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=bug-26138-9773@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).