From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: -Wall
Date: Mon, 04 Apr 2016 20:58:36 +0200 [thread overview]
Message-ID: <m3shz1mc9v.fsf@gnus.org> (raw)
In-Reply-To: <5702B7C9.6010805@cs.ucla.edu> (Paul Eggert's message of "Mon, 4 Apr 2016 11:51:53 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 04/04/2016 11:22 AM, Lars Magne Ingebrigtsen wrote:
>> There's a lot fewer warnings when compiling with -Wall in emacs/src now
>> than there used to be, but there should be none, I think.
>
> I'm getting no warnings when I build.
Hm... I just added -Wall to the options line in the Makefile, and I get
a couple dozen. But examining most of these more closely, they're the
result of this:
RGB_PIXEL_COLOR corner_pixels[4], best IF_LINT (= 0);
So I guess the IF_LINT is triggered by... something?
Anyway, if you're not seeing any warnings with the setup you're using,
shouldn't those options be the default compilation options?
> It's more the other way around: -Wall doesn't generate enough
> warnings. Please try './configure --enable-gcc-warnings'. This uses
> -Wall plus some other warning flags that are useful in practice. I
> regularly check that this builds cleanly for recent GCC on my platform
> (Fedora 23, GCC 5.3.1 20151207 (Red Hat 5.3.1-2)), and occasionally
> for recent Ubuntu, both using default configure-time options.
>
> If you'd like to take up the burden of porting --enable-gcc-warnings
> to other platforms feel free, though my suggestion is to not bother
> with older and/or rarely-used platforms as they have too many bugs in
> this area.
How about making that option the default on GNU/Linux systems? There
would be less code for you to clean up after I've done C level changes
and forgotten to twiddle the options. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-04 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:22 -Wall Lars Magne Ingebrigtsen
2016-04-04 18:51 ` -Wall Paul Eggert
2016-04-04 18:58 ` Lars Magne Ingebrigtsen [this message]
2016-04-05 0:20 ` -Wall Paul Eggert
2016-04-05 7:39 ` -Wall Lars Magne Ingebrigtsen
2016-04-05 14:35 ` -Wall Eli Zaretskii
2016-04-05 15:12 ` -Wall Paul Eggert
2016-04-06 11:49 ` -Wall Lars Magne Ingebrigtsen
2016-04-06 12:02 ` -Wall Stefan Monnier
2016-04-07 5:16 ` -Wall Paul Eggert
2016-04-04 23:22 ` -Wall John Wiegley
2016-04-05 13:16 ` -Wall Philipp Stephani
2016-04-05 14:46 ` -Wall Eli Zaretskii
2016-04-05 15:09 ` -Wall John Wiegley
2016-04-05 14:54 ` -Wall Richard Stallman
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=m3shz1mc9v.fsf@gnus.org \
--to=larsi@gnus.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.