From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rcopley@gmail.com, emacs-devel@gnu.org
Subject: Re: GCC 7 warnings
Date: Sat, 9 Sep 2017 13:30:02 -0700 [thread overview]
Message-ID: <420e8469-173b-ab3b-b401-4fbb4a8a42b5@cs.ucla.edu> (raw)
In-Reply-To: <83lglnvffp.fsf@gnu.org>
Eli Zaretskii wrote:
> Since --enable-gcc-warnings is on by default for building the
> development version, it needs to build relatively cleanly with a
> reasonably recent GCC. It's okay to have the code ready for the
> bleeding edge, but if that triggers warnings with slightly older GCC,
> it's counter-productive IMO, because asking developers to use GCC
> which is too new might waste their time due to GCC bugs. GCC 6 or 5
> is not yet old enough to cause those who use them such trouble.
GCC 5.4 is OK. I still test with it, at times. Not sure it's worth going back
further than that though, for developers.
I don't use bleeding-edge GCC, which is GCC 8 (not released yet). I haven't
even upgraded yet to the latest stable release, 7.2.0. So I'm not really
bleeding-edge.
In my experience GCC 7 is more reliable than older versions, for compiling C
programs. I don't recommend using GCC 8 for production, though.
The point of the May 2016 cleanup was to remove gorp like UNINIT (and it is
admittedly awkward) when GCC had gotten smart enough that the gorp wasn't
needed. Unfortunately there is no easy way to make UNINIT's syntax C-like, at
least not with current GCC. In the meantime UNINIT's technical advantages
outweigh its stylistic awkwardness.
prev parent reply other threads:[~2017-09-09 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 16:16 GCC 7 warnings Eli Zaretskii
2017-09-09 18:27 ` Paul Eggert
2017-09-09 19:29 ` Eli Zaretskii
2017-09-09 20:30 ` Paul Eggert [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=420e8469-173b-ab3b-b401-4fbb4a8a42b5@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rcopley@gmail.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.
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.