public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Nick Clifton <nickc@redhat.com>, gcc@gcc.gnu.org
Cc: Joseph Myers <joseph@codesourcery.com>
Subject: Re: November 2016 GNU Toolchain Update
Date: Sun, 12 Mar 2017 22:10:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1703122308330.3498@anthias.pfeifer.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611160058010.2244@digraph.polyomino.org.uk>

On Tue, 15 Nov 2016, Nick Clifton wrote:
> That's all for now.  Hopefully the next update will be a bit sooner in
> arriving.

Thanks for that update, Nick.  Surely interesting reading.
Are you planning another update for March or so? ;-)

On Wed, 16 Nov 2016, Joseph Myers wrote:
> Many of the GCC features listed here are not mentioned in 
> gcc-7/changes.html.  We all need to expand that to be more thorough in 
> covering features that are new in GCC 7 compared to GCC 6.

In the meantime there have been many additions to gcc-7/changes.html,
and I believe except for

    + -Wbool-operation warns about suspicious operations on
      expressions of a boolean type.  For instance, bitwise negation
      of a boolean is very likely a bug in the program.  For C, this
      warning also warns about incrementing or decrementing a boolean,
      which rarely makes sense.

everything should be more or less covered now.

Still, additions very welcome, guys.  Let me know if you need help.

Gerald

  reply	other threads:[~2017-03-12 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 13:12 Nick Clifton
2016-11-16  0:59 ` Joseph Myers
2017-03-12 22:10   ` Gerald Pfeifer [this message]
2017-03-14 13:42     ` Nick Clifton

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=alpine.LSU.2.20.1703122308330.3498@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=nickc@redhat.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).