All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: bump 7.x series to 7.2.0
Date: Thu, 17 Aug 2017 19:44:25 +0200	[thread overview]
Message-ID: <20170817194425.62504831@windsurf> (raw)
In-Reply-To: <20170816203025.22554-1-thomas.petazzoni@free-electrons.com>

Hello,

On Wed, 16 Aug 2017 22:30:25 +0200, Thomas Petazzoni wrote:

> I'm not sure whether we want this for master or next. I've built 71
> toolchains with GCC 7.2.0 for toolchains.free-electrons.com, the vast
> majority of them being then used to build and boot a Linux kernel +
> minimal userspace under Qemu.
> 
> Unfortunately, the tag gcc-7_2_0-release has still not appeared in
> git://gcc.gnu.org/git/gcc.git, so it's hard to see the amount of
> changes between gcc 7.1.0 and gcc 7.2.0.
> 
> According to the release e-mail at
> https://gcc.gnu.org/ml/gcc/2017-08/msg00129.html:
> 
> """
> GCC 7.2 is a bug-fix release from the GCC 7 branch
> containing important fixes for regressions and serious bugs in
> GCC 6.1 with more than 95 bugs fixed since the previous release.
> """
> 
> Perhaps the safest is to take this in next.

Rethinking this: gcc 7.x is not the default gcc version currently used
in Buildroot, so I think bumping the 7.x series to 7.2.0 is quite safe
for the 2017.08 release.

However, I don't really mind, so I'll let others give their opinion on
this.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-08-17 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 20:30 [Buildroot] [PATCH] gcc: bump 7.x series to 7.2.0 Thomas Petazzoni
2017-08-16 20:47 ` Andrey Yurovsky
2017-08-17 17:44 ` Thomas Petazzoni [this message]
2017-08-18 16:49   ` Bernd Kuhls
2017-08-17 22:17 ` Arnout Vandecappelle
2017-08-21 21:31   ` Thomas Petazzoni
2017-08-21 21:31 ` Thomas Petazzoni

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=20170817194425.62504831@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 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.