From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] package/gcc: add support for gcc 10
Date: Wed, 24 Jun 2020 21:55:39 +0200 [thread overview]
Message-ID: <20200624215539.078dfb99@windsurf> (raw)
In-Reply-To: <20200608221347.2639059-2-romain.naour@gmail.com>
On Tue, 9 Jun 2020 00:13:44 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> Keep the same patch as for gcc 9.x fixing a parallel build issue:
> 58ecbbc3ef18c43ae1c02a5c4bf30aa7ef2d8092.
>
> Keep libzstd support disabled for now, it could be used to LTO bytecode.
"... it could be used for LTO bytecode compression", otherwise it
doesn't make a lot of sense.
I've applied, but I have some comments/questions below.
> +config BR2_GCC_VERSION_10_X
> + bool "gcc 10.x"
> + # or1k needs binutils >= 2.32
> + depends on !(BR2_or1k && BR2_BINUTILS_VERSION_2_31_X)
Why are we doing this here, instead of in the binutils package ? This
looks strange.
> + # powerpc spe support has been deprecated since gcc 8.x.
> + # https://gcc.gnu.org/ml/gcc/2018-04/msg00102.html
> + depends on !BR2_powerpc_SPE
Should we now drop support for PowerPC SPE ?
> + # C-SKY sk610 needs abiv1, which is not supported in
> + # upstream gcc. C-SKY gcc upstream support not tested
> + # with upstream binutils and glibc.
> + depends on !BR2_csky
We haven't had any news/contribution for C-SKY people for quite a
while. I know in recent SoC they have used RISC-V cores, but they were
supposed to continue making C-SKY based SoCs. I am fearing that this
looks like yet another abandoned CPU architecture :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-24 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 22:13 [Buildroot] [PATCH 1/5] toolchain: add gcc 10 entry Romain Naour
2020-06-08 22:13 ` [Buildroot] [PATCH 2/5] package/gcc: add support for gcc 10 Romain Naour
2020-06-24 19:55 ` Thomas Petazzoni [this message]
2020-06-24 20:38 ` Romain Naour
2020-06-08 22:13 ` [Buildroot] [PATCH 3/5] arch: add BR2_ARCH_NEEDS_GCC_AT_LEAST_10 Romain Naour
2020-06-24 19:55 ` Thomas Petazzoni
2020-06-08 22:13 ` [Buildroot] [PATCH 4/5] toolchain-external: add gcc 10 entry Romain Naour
2020-06-24 19:55 ` Thomas Petazzoni
2020-06-08 22:13 ` [Buildroot] [PATCH 5/5] package/gcc: switch to gcc 9.x as the default Romain Naour
2020-06-24 19:56 ` Thomas Petazzoni
2020-06-24 20:41 ` Romain Naour
2020-07-07 13:13 ` Peter Korsgaard
2020-08-29 12:13 ` Peter Korsgaard
2020-06-24 19:53 ` [Buildroot] [PATCH 1/5] toolchain: add gcc 10 entry 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=20200624215539.078dfb99@windsurf \
--to=thomas.petazzoni@bootlin.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.