From: Tom Tromey <tromey@cygnus.com>
To: ADAM Sulmicki <adam@cfar.umd.edu>
Cc: java-discuss@sourceware.cygnus.com
Subject: Re: gcj and '-Wall'?
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200002270743.XAA28802@ferrule.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.95.1000226220805.19569T-100000@chia.umiacs.umd.edu>
>>>>> "Adam" == ADAM Sulmicki <adam@cfar.umd.edu> writes:
Adam> It seems that '-Wall' is not supported with gcj.
Adam> Is this correct?
-Wall is supported. It just doesn't do what you think.
Adam> I was hoping to use gcj to let me
Adam> know about any unused variables, and any other possible
Adam> bugs..
Use -Wunused. This is apparently a general gcc option. It works with
gcj (but, unfortunately, on your example it prints too much -- a
lurking gcj bug).
I agree that gcj should enable -Wunused when -Wall is given, because
that is similar to what the C compiler does. I consider this a bug in
gcj. I'll submit a patch.
Tom
prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 0:00 ADAM Sulmicki
2000-04-01 0:00 ` Bryce McKinlay
2000-04-01 0:00 ` Tom Tromey [this message]
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=200002270743.XAA28802@ferrule.cygnus.com \
--to=tromey@cygnus.com \
--cc=adam@cfar.umd.edu \
--cc=java-discuss@sourceware.cygnus.com \
/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).