public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/26138] Lots of warnings with gcj .jar -> .so
Date: Tue, 07 Feb 2006 19:23:00 -0000	[thread overview]
Message-ID: <20060207192342.22967.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26138-9773@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from tromey at gcc dot gnu dot org  2006-02-07 19:23 -------
I looked at this a bit more.

We don't want to set TREE_USED on the itable syms decl, because
that will still cause it to be emitted, even though it is not used.
It would be preferable to not create the various decls here unless we
know for sure that they will be used.


-- 


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


  parent reply	other threads:[~2006-02-07 19:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 20:36 [Bug java/26138] New: " overholt at redhat dot com
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 [this message]
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=20060207192342.22967.qmail@sourceware.org \
    --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).