linux-kernel - Re: [GIT PULL] arch: remove obsolete architecture ports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 02 Apr 2018 19:57:13 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     Arnd Bergmann <arnd@...db.de>
CC:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
        jhogan@...nel.org, dhowells@...hat.com, linux-am33-list@...hat.com,
        takata@...ux-m32r.org, lennox.wu@...il.com, Aaron.Wu@...log.com,
        cooloney@...il.com, chris.d.metcalf@...il.com,
        jesper.nilsson@...s.com
Subject:     Re: [GIT PULL] arch: remove obsolete architecture ports

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 :).