linux-kernel - Re: [gnu-csky] [PATCH 00/19] C-SKY(csky) Linux Kernel Port

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, 26 Mar 2018 17:11:45 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Sandra Loosemore <sandra@...esourcery.com>
Cc:     Guo Ren <ren_guo@...ky.com>,
        linux-arch <linux-arch@...r.kernel.org>,
        Jason Cooper <jason@...edaemon.net>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        c-sky_gcc_upstream@...ky.com, wbx@...ibc-ng.org,
        thomas.petazzoni@...tlin.com, gnu-csky@...tor.com,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [gnu-csky] [PATCH 00/19] C-SKY(csky) Linux Kernel Port

On Mon, Mar 26, 2018 at 5:06 PM, Sandra Loosemore
<sandra@...esourcery.com> wrote:
> On 03/26/2018 07:30 AM, Arnd Bergmann wrote:
>>
>>
>> Another interesting question is the status of your toolchain support. I
>> see your
>> github account contains binutils and gcc repositories, but they are not
>> upstream
>> yet. Are you working on getting those included in the respective upstream
>> projects already?
>
>
> We at Mentor Graphics are working on preparing the abiv2 binutils and gcc
> support for upstream submission.  The existing gcc back end for abiv1 is
> actually completely separate from the abiv2 back end and probably eventually
> needs to be merged with it, but first things first.

Ok, very good. Being able to build abiv2 is probably sufficient for testing
the kernel in a meaningful way, and if you are working on getting that
upstream, I trust that it will happen quick enough. I can always provide
toolchain binaries on kernel.org based a prerelease version like I did
for openrisc, which makes it accessible to other kernel developers doing
cross-arch changes.

      Arnd