From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Problems with --enable-gcc-warnings
Date: Tue, 17 Dec 2013 19:57:52 +0200 [thread overview]
Message-ID: <83ppovcqcf.fsf@gnu.org> (raw)
I tried that option in several systems and saw a few problems I
thought I should mention here.
First, it seems like older compilers have trouble with some of the
warning options. On one system, which has GCC 3.4, I see this:
cc1.exe: warning: command line option "-Wabi" is valid for C++/ObjC++ but not for C
cc1.exe: warning: command line option "-Wdeprecated" is valid for C++/Java/ObjC++ but not for C
On another system, which has GCC 4.4 (fencepost.gnu.org), I see this:
cc1: warning: command line option "-Wenum-compare" is valid for C++/ObjC++ but not for C
If these options are not universally supported, why doesn't configure
make some real test, and avoid using those if they are not supported
for C programs? Alternatively, if these warnings are not supposed to
be turned on unless GCC is of some relatively new version, why isn't
that being tested?
Then I had a warning in lib/file-has-acl.c, because under some
conditions the acl_access_nontrivial doesn't return a value (look near
its end).
Lastly, the INT_BUFSIZE_BOUND macro seems to be unable to support
'void *' as its argument without emitting warnings, I need to use
intptr_t instead to pacify the compiler.
Thanks.
next reply other threads:[~2013-12-17 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 17:57 Eli Zaretskii [this message]
2013-12-17 20:49 ` Problems with --enable-gcc-warnings Paul Eggert
2013-12-17 21:08 ` Eli Zaretskii
2013-12-17 22:20 ` Paul Eggert
2013-12-18 3:50 ` Eli Zaretskii
2013-12-18 4:13 ` Paul Eggert
2013-12-18 16:17 ` Eli Zaretskii
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=83ppovcqcf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.