From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Julien Corjon <corjon.j@ecagroup.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] toolchain: remove gcc bug 90620
Date: Thu, 9 May 2024 17:48:34 +0200 [thread overview]
Message-ID: <20240509174834.46a63d72@windsurf> (raw)
In-Reply-To: <05114d73-760c-4a56-b655-3d0268158ddf@benettiengineering.com>
On Sun, 28 Apr 2024 20:35:30 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> But this bug is Microblaze specific and the only 2 Microblaze external
> toolchains are the Bootlin's ones, where the oldest GCC version is
> 12.3.0, so as we've already done in the past with this commit:
> https://gitlab.com/buildroot.org/buildroot/-/commit/55fcba2a7c41d29f3f93bb37eec1264af4b45fb0
>
> considering Buildroot free of bug 90620. If anyone will send a patch
> for new microblaze external-toolchains it's very unlikely they will
> contain gcc < 10.
Arnout's point is not about new toolchains (which will indeed be based
on a recent gcc), but rather on older custom external toolchains that
people might still be using.
I don't have a hard feeling on this one. Yes, supporting old external
toolchains is nice. On the other hand, at some point, we need to get
rid of those workarounds, but I'm not sure when is the good time.
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
next prev parent reply other threads:[~2024-05-09 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 7:49 [Buildroot] [PATCH] toolchain: remove gcc bug 90620 Giulio Benetti
2024-04-28 17:18 ` Arnout Vandecappelle via buildroot
2024-04-28 18:35 ` Giulio Benetti
2024-05-09 15:48 ` Thomas Petazzoni via buildroot [this message]
2024-05-09 20:19 ` Arnout Vandecappelle 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=20240509174834.46a63d72@windsurf \
--to=buildroot@buildroot.org \
--cc=corjon.j@ecagroup.com \
--cc=fontaine.fabrice@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--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 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.