Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: Gary Thomas <gary@mlbassoc.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Future of GCC
Date: Tue, 12 Jul 2016 23:27:15 +0100	[thread overview]
Message-ID: <1468362435.28829.118.camel@linuxfoundation.org> (raw)
In-Reply-To: <5785627D.9080800@gmail.com>

On Tue, 2016-07-12 at 14:34 -0700, akuster808 wrote:
> 
> On 07/12/2016 02:24 PM, Burton, Ross wrote:
> > On 12 July 2016 at 22:14, akuster808 <akuster808@gmail.com> wrote:
> > 
> > > > Personally I was thinking that gcc 5.x and 6.x should stay in
> > > > oe-core for
> > > > this cycle, and then drop 5.x after the release.
> > > 
> > > 
> > > Wouldn't that be dropped iff GCC 7.0 is release? or are you
> > > saying we
> > > should only have one GCC version?
> > > 
> > 
> > Well, depends on the adoption and migration problems.  I don't
> > think we
> > should carry three versions,
> 
> I agree. 3 is too many.
> 
>  and ideally one, but two is acceptable to ease
> > migration.
> 
> One makes Stable maintenance less costly in time.

I'm personally a fan of one if we can do it. We've taken a bit of an
"easier" path recently but it might be time to change that. Right now
I'm not aware of any of our core usecases which need 5.x, all work with
6.x. I am aware of some BSPs on older kernels which would however have
issues.

I did nearly send a 5.x removal patch but wasn't sure it would be
accepted by people quite yet...

Cheers,

Richard



  reply	other threads:[~2016-07-12 22:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  7:57 Future of GCC Gary Thomas
2016-07-12  8:15 ` Burton, Ross
2016-07-12 21:14   ` akuster808
2016-07-12 21:24     ` Burton, Ross
2016-07-12 21:34       ` akuster808
2016-07-12 22:27         ` Richard Purdie [this message]
2016-07-12 23:15           ` Khem Raj
2016-07-13 12:46           ` Martin Jansa

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=1468362435.28829.118.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.com \
    --cc=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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