Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/gcc: add support for gcc 7
Date: Wed, 24 May 2017 16:26:12 +0200	[thread overview]
Message-ID: <20170524162612.09a18a25@free-electrons.com> (raw)
In-Reply-To: <20170523202440.6949-2-romain.naour@gmail.com>

Hello,

First of all, thanks for doing this work!

I've added Alexey, Waldemar and Vicente in Cc, since there are some
ARC, Microblaze, OpenRISC and MIPS questions below.

On Tue, 23 May 2017 22:24:39 +0200, Romain Naour wrote:
> Remove upstream patches:

[...]

Nice to see that so many patches are upstream, and that our stack of
gcc patches for 7.x is now really small!

Perhaps we should start some effort to upstream the last few remaining
patches?

> +config BR2_GCC_VERSION_7_X
> +	bool "gcc 7.x"
> +	# Broken or unsupported architectures
> +	depends on !BR2_arc
> +	depends on !BR2_microblaze
> +	depends on !BR2_or1k

ARC is indeed still not supported fully in gcc 7.x I believe. Alexey,
do you confirm?

But what is the problem with Microblaze? And with OpenRISC? Waldemar?

OpenRISC has its own gcc version, so I guess that's the answer. But
what about Microblaze?

> +	# Unsupported MIPS cores
> +	depends on !BR2_mips_m6250 && !BR2_mips_p6600

Vicente, what is the status of the support for those MIPS cores in gcc
7.x ?

Romain: I think we should also default to gcc 6.x now instead of
defaulting to gcc 5.x.

And perhaps we should start thinking about removing gcc 4.9.x as well.
For toolchain components, I don't think it makes sense to support more
than three versions, i.e:

 1. old one (would be 5.x now)
 2. default one (would be 6.x now)
 3. bleeding edge one (would be 7.x now)

Thanks!

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

  reply	other threads:[~2017-05-24 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 20:24 [Buildroot] [PATCH v2 1/3] package/uclibc: add upstream patch to fix build issue with gcc7 Romain Naour
2017-05-23 20:24 ` [Buildroot] [PATCH v2 2/3] package/gcc: add support for gcc 7 Romain Naour
2017-05-24 14:26   ` Thomas Petazzoni [this message]
2017-05-24 14:37     ` Waldemar Brodkorb
2017-05-24 14:47     ` Alexey Brodkin
2017-05-25 17:52     ` Romain Naour
2017-05-23 20:24 ` [Buildroot] [PATCH v2 3/3] package/gcc: remove gcc 4.8 Romain Naour
2017-05-24 14:21 ` [Buildroot] [PATCH v2 1/3] package/uclibc: add upstream patch to fix build issue with gcc7 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=20170524162612.09a18a25@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox