From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 15/15] package/gcc: enable gcc 9.1 for ork1 (openrisc)
Date: Sun, 14 Jul 2019 11:39:16 +0200 [thread overview]
Message-ID: <20190714093916.GK2680@scaer> (raw)
In-Reply-To: <CAJF2gTSD9ANSQs7S3nSnboZm7P012mzO1EfuE-P4Z5xFusvSYw@mail.gmail.com>
Guo, All,
Peter, Thomas, Arnout, question below...
On 2019-07-14 17:18 +0800, Guo Ren spake thusly:
> On Sun, Jul 14, 2019 at 4:41 PM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2019-07-14 07:57 +0800, Guo Ren spake thusly:
> > > On Sun, Jul 14, 2019 at 5:24 AM Arnout Vandecappelle <arnout@mind.be> wrote:
> > > > On 20/06/2019 12:07, Giulio Benetti wrote:
> > > > > openrisc support has been added with gcc 9.1.
> > > > > Keep for now the old gcc 5 fork for ork1.
> > > > So, when will we remove this?
> > > > Same for ARC (GCC 8.x fork) and C-SKY (GCC 6.x fork): they are available in
> > > > GCC9, do we need to keep those old forks?
> > > Keep the fork for C-SKY, the upstream of csky backend in gcc9 only
> > > support abiv2.
> > As far as I can see, we have no way to choose the ABI in Buildroot.
> > So, what would we loose by keeping only gcc-9?
> See package/Makefile.in
>
> # For C-SKY abiv1 & abiv2
> ifeq ($(BR2_csky),y)
> ifeq ($(BR2_ck610),y)
> ABI = abiv1
> else
> ABI = abiv2
> endif
> endif
Ah, thanks for pointing this out. I only had a look at arch/arch.mk.csky
and arch/Config.in.csky.
This makes me wonder: should we move all this out of package/Makefile.in
and into the per-arch .mk files instead?
> gcc-9 don't support 610.
There is currently nothign in Buildroot that prevents selecting gcc9 for
the ck610...
>
> --
> Best Regards
> Guo Ren
>
> ML: https://lore.kernel.org/linux-csky/
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-07-14 9:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 10:07 [Buildroot] [PATCH v4 00/15] Add gcc 9.1 Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 01/15] package/glibc/arc: fix build issue with gcc-9.1 Giulio Benetti
2019-06-22 18:58 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 02/15] linux: disable Werror for powerpc kernels Giulio Benetti
2019-06-22 18:59 ` Thomas Petazzoni
2019-06-24 20:15 ` Peter Korsgaard
2019-06-25 3:05 ` Baruch Siach
2019-06-25 6:18 ` Peter Korsgaard
2019-06-20 10:07 ` [Buildroot] [PATCH v4 03/15] package/uclibc: remove asm constraint Giulio Benetti
2019-06-22 19:31 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 04/15] toolchain: add gcc 9 entry Giulio Benetti
2019-06-22 19:39 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 05/15] package/gcc: add support for gcc 9.1 Giulio Benetti
2019-06-22 19:40 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 06/15] arch: add BR2_ARCH_NEEDS_GCC_AT_LEAST_9 Giulio Benetti
2019-06-22 19:41 ` Thomas Petazzoni
2019-06-23 9:26 ` Peter Korsgaard
2019-06-20 10:07 ` [Buildroot] [PATCH v4 07/15] toolchain-external: add gcc 9 entry Giulio Benetti
2019-06-22 19:42 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 08/15] package/gcc: switch to gcc 8.x as the default Giulio Benetti
2019-06-22 19:44 ` Thomas Petazzoni
2019-06-22 22:35 ` Romain Naour
2019-06-23 16:21 ` Thomas Petazzoni
2019-06-24 6:35 ` Peter Korsgaard
2019-06-25 22:25 ` Arnout Vandecappelle
2019-06-26 6:55 ` Romain Naour
2019-06-26 7:23 ` Thomas Petazzoni
2019-06-26 7:34 ` Romain Naour
2019-06-26 6:55 ` Thomas Petazzoni
2019-06-23 9:29 ` Peter Korsgaard
2019-06-20 10:07 ` [Buildroot] [PATCH v4 09/15] arch/arm: move dependency on 64-bit down to individual cores Giulio Benetti
2019-07-13 21:11 ` Arnout Vandecappelle
2019-06-20 10:07 ` [Buildroot] [PATCH v4 10/15] arch/arm: some cores have a different name with gcc-9 Giulio Benetti
2019-07-13 21:13 ` Arnout Vandecappelle
2019-07-13 21:33 ` Yann E. MORIN
2019-06-20 10:07 ` [Buildroot] [PATCH v4 11/15] arch/arm: saphira is in fact an armv8.4a Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 12/15] arch/arm: add two new 64-bit-only armv8a cores Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 13/15] arch/arm: add two new cortex-based armv8.2a cores Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 14/15] arch/arm: add two new non-cortex-based " Giulio Benetti
2019-07-13 21:22 ` Arnout Vandecappelle
2019-07-13 21:51 ` Yann E. MORIN
2019-06-20 10:07 ` [Buildroot] [PATCH v4 15/15] package/gcc: enable gcc 9.1 for ork1 (openrisc) Giulio Benetti
2019-07-13 21:24 ` Arnout Vandecappelle
2019-07-13 23:57 ` Guo Ren
2019-07-14 8:40 ` Yann E. MORIN
2019-07-14 9:18 ` Guo Ren
2019-07-14 9:39 ` Yann E. MORIN [this message]
2019-07-14 10:00 ` Thomas Petazzoni
2019-07-14 10:08 ` Yann E. MORIN
2019-07-14 12:48 ` Romain Naour
2019-07-15 21:55 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
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=20190714093916.GK2680@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox