Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	ARC Buildroot mailing list <arc-buildroot@synopsys.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] ARC support in Buildroot
Date: Sat, 12 Aug 2023 00:25:03 +0200	[thread overview]
Message-ID: <20230812002503.33f6d5c3@windsurf> (raw)
In-Reply-To: <cc38f5ec-c613-2323-e288-7fc1d0b186b6@mind.be>

Hello,

On Fri, 11 Aug 2023 22:00:48 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

> > So, in theory it should be OK to remove "arc-xxxx.yy" toolchains from Buildroot.
> > But since we were a bit late with ARCv3 changes for GCC 13, those will only
> > land in GCC 14 which is going to happen sometime in 2024, I guess.  
> 
>   I think (Thomas correct me if I'm wrong) that we would actually prefer that 
> ARC just uses the normal toolchain, and that when ARCv3 is introduced in 
> Buildroot, the "special toolchain" will depend on 
> BR2_arc_v3_or_whatever_it_will_be_called rather than BR2_arc.

[...]

>   Using the upstream toolchain components is preferred because that way the user 
> has the version choice, rather than being forced to use the ARC-specific version 
> of that moment. Also, when someone updates to a new GCC version, it immediately 
> becomes available for ARC as well (instead of having to wait 3 years for the 
> ARC-specific version to be updated...).

This is a very good point indeed.

Alexey: when do you expect to submit ARCv3 support in Buildroot?
Depending on when it comes we might decide to either drop or keep the
ARC-specific toolchain components, and if need be re-introduce them for
ARCv3.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-08-11 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 20:03 [Buildroot] ARC support in Buildroot Thomas Petazzoni via buildroot
2023-08-02 21:20 ` Alexey Brodkin via buildroot
2023-08-02 22:12   ` Thomas Petazzoni via buildroot
2023-08-03  7:59     ` Alexey Brodkin via buildroot
2023-08-06 20:51       ` Thomas Petazzoni via buildroot
2023-08-06 21:10         ` Thomas Petazzoni via buildroot
2023-08-11 20:00       ` Arnout Vandecappelle via buildroot
2023-08-11 22:25         ` Thomas Petazzoni via buildroot [this message]
2023-08-11 22:34           ` Alexey Brodkin via buildroot
2023-08-12  8:38             ` Thomas Petazzoni via buildroot

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=20230812002503.33f6d5c3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=arc-buildroot@synopsys.com \
    --cc=arnout@mind.be \
    --cc=thomas.petazzoni@bootlin.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