From: Palmer Dabbelt <palmer@sifive.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
jhogan@kernel.org, dhowells@redhat.com,
linux-am33-list@redhat.com, takata@linux-m32r.org,
lennox.wu@gmail.com, Aaron.Wu@analog.com, cooloney@gmail.com,
chris.d.metcalf@gmail.com, jesper.nilsson@axis.com
Subject: Re: [GIT PULL] arch: remove obsolete architecture ports
Date: Mon, 02 Apr 2018 19:57:13 -0700 (PDT) [thread overview]
Message-ID: <mhng-ef075a77-24a8-4764-bb5d-c4b06722c0bb@palmer-si-x1c4> (raw)
In-Reply-To: <CAK8P3a0q70FYtBaCcsBPejVULgsbJPwUG7QmrkU9NJpr7oTzpQ@mail.gmail.com>
On Mon, 02 Apr 2018 00:17:30 PDT (-0700), Arnd Bergmann wrote:
> - openrisc, risc-v and nds32 are still in the process of finishing their
> support or getting it added to mainline gcc in the first place.
> They all have patched gcc-7.3 ports that work to some degree, but
> complete upstream support won't happen before gcc-8.1. Csky posted
> their first kernel patch set last week, their situation will be similar.
FWIW, RISC-V landed in GCC 7. The 7.3.0 release (and binutils-2.30) is the
first one we recommend for kernel development as there have been a handful of
bug fixes, but there's nothing major. SiFive ships GCC versions with a few
extra patches applied, and while I still recommend people use these they should
all be performance improvements at this point. With compilers you never know
if a performance improvement is hiding a bug, but what's tagged as gcc-7.3.0
passes the test suite.
Our 32-bit glibc port isn't upstream yet, but our 32-bit kernel is a bit of a
mess so that's not the blocking issue in rv32-land right now :).
next prev parent reply other threads:[~2018-04-03 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 7:17 [GIT PULL] arch: remove obsolete architecture ports Arnd Bergmann
2018-04-02 18:57 ` Linus Torvalds
2018-04-02 19:54 ` Arnd Bergmann
2018-04-03 9:18 ` Geert Uytterhoeven
2018-04-04 8:01 ` Pavel Machek
2018-04-04 8:38 ` Arnd Bergmann
2018-04-04 13:28 ` James Hogan
2018-04-03 2:57 ` Palmer Dabbelt [this message]
2018-04-03 4:08 ` Linus Torvalds
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=mhng-ef075a77-24a8-4764-bb5d-c4b06722c0bb@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=Aaron.Wu@analog.com \
--cc=arnd@arndb.de \
--cc=chris.d.metcalf@gmail.com \
--cc=cooloney@gmail.com \
--cc=dhowells@redhat.com \
--cc=jesper.nilsson@axis.com \
--cc=jhogan@kernel.org \
--cc=lennox.wu@gmail.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=takata@linux-m32r.org \
--cc=torvalds@linux-foundation.org \
/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.