All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/gcc: add support for gcc 7
Date: Wed, 24 May 2017 14:47:50 +0000	[thread overview]
Message-ID: <1495637269.2909.25.camel@synopsys.com> (raw)
In-Reply-To: <20170524162612.09a18a25@free-electrons.com>

Hi Thomas, all,

On Wed, 2017-05-24 at 16:26 +0200, Thomas Petazzoni wrote:
> 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?

Well I'd say something completely opposite :)

GCC 7.x has as much of ARC support as it could be now. We submit all our changes
to gcc immediately and it's only a matter of review and approval delay for when it
lands in master branch of GCC. The same applies to GCC releases - whatever got merged
by the time of release is there. So I'd say we barely differ here a lot from other first
class citizens in GCC.

Moreover GCC 7.1 should work for us just fine and very limited amount of patches could
be needed to fix things here and there.

BTW and the same is true for Binutils. And frankly for quite some time now I was planning
to give upstream GCC/Binutils a try in Buildroot for ARC. So while we're on topic I guess
we may start from having 2 options for ARC users:
?* Build toolchain from ARC releases from GitHub forks of GCC and Binutils
?* Build toolchain from upstream releases

-Alexey

  parent reply	other threads:[~2017-05-24 14:47 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
2017-05-24 14:37     ` Waldemar Brodkorb
2017-05-24 14:47     ` Alexey Brodkin [this message]
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=1495637269.2909.25.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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.