From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gcc: Enable gcc-8.x support for BR2_powerpc_spe
Date: Tue, 3 Nov 2020 21:37:06 +0100 [thread overview]
Message-ID: <5fd0508f-8598-4cea-6451-34cbdd382fae@gmail.com> (raw)
In-Reply-To: <20201031234922.3653a68a@windsurf>
Hello,
Le 31/10/2020 ? 23:49, Thomas Petazzoni a ?crit?:
> On Mon, 26 Oct 2020 15:17:35 -0400
> Michael Durrant <mdurrant@ArcturusNetworks.com> wrote:
>
>> The GCC-7.x compiler series was the last to support BR2_powerpc_SPE CPUs
>> within GCC.? After GCC-7.x support was removed as a default in buildroot,
>> some boards, including the arcturus_ucp1020_defconfig and
>> freescale_p1025twr_defconfig will fail to compile.
>>
>> The GCC-8.x compiler series continues to support powerpc_spe CPU
>> cores, but only as an --enable-obsoleted instruction set.
>> This patch enables the use of GCC-8.x and asserts the required
>> option to enable the powerpc_spe instruction set.
This is sad to see a CPU that is still used removed from upstream GCC.
But what's the plan for next year ? GCC 8 is currently at 8.4.0 and the last
release will be available in few month.
As soon as GCC 11.1 is added to Buildroot, GCC 8 will likely be removed to keep
only 3 GCC version.
I don't see a future proof solution... maybe using a prebuilt toolchain for this
defconfig?
Best regards,
Romain
>>
>> This Patch passes compilation and run tests with the
>> arcturus/ppc-ucp1020? board.
>>
>> Tested-by: Oleksandr G Zhadan <Oleks@ArcturusNetworks.com>
>>
>> This patch should address a noted job failure on GitLab CI
>> https://gitlab.com/buildroot.org/buildroot/-/jobs/805461732
>>
>> Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/805461732
>> Signed-off-by: Oleksandr G Zhadan <Oleks@ArcturusNetworks.com>
>> Signed-off-by: Michael Durrant <mdurrant@ArcturusNetworks.com>
>> ---
>> ?package/gcc/Config.in.host | 2 +-
>> ?package/gcc/gcc.mk???????? | 1 +
>> ?2 files changed, 2 insertions(+), 1 deletion(-)
>
> Applied to master, thanks.
>
> Thomas
>
prev parent reply other threads:[~2020-11-03 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9aeb0cb1-00e7-702a-0d41-f6471e6f0302@ArcturusNetworks.com>
2020-10-26 19:17 ` [Buildroot] [PATCH 1/1] package/gcc: Enable gcc-8.x support for BR2_powerpc_spe Michael Durrant
2020-10-27 15:03 ` Matthew Weber
2020-10-28 14:56 ` Oleksandr G Zhadan
2020-10-31 22:49 ` Thomas Petazzoni
2020-11-03 20:37 ` Romain Naour [this message]
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=5fd0508f-8598-4cea-6451-34cbdd382fae@gmail.com \
--to=romain.naour@gmail.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.