From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [gnu-csky] [PATCH 00/19] C-SKY(csky) Linux Kernel Port Date: Mon, 26 Mar 2018 17:11:45 +0200 Message-ID: References: <8f76538a-27a4-745e-3d28-db3be06e9715@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <8f76538a-27a4-745e-3d28-db3be06e9715@codesourcery.com> Sender: linux-kernel-owner@vger.kernel.org To: Sandra Loosemore Cc: Guo Ren , linux-arch , Jason Cooper , Daniel Lezcano , Linux Kernel Mailing List , c-sky_gcc_upstream@c-sky.com, wbx@uclibc-ng.org, thomas.petazzoni@bootlin.com, gnu-csky@mentor.com, Thomas Gleixner List-Id: linux-arch.vger.kernel.org On Mon, Mar 26, 2018 at 5:06 PM, Sandra Loosemore 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f195.google.com ([209.85.216.195]:36298 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751868AbeCZPLr (ORCPT ); Mon, 26 Mar 2018 11:11:47 -0400 MIME-Version: 1.0 In-Reply-To: <8f76538a-27a4-745e-3d28-db3be06e9715@codesourcery.com> References: <8f76538a-27a4-745e-3d28-db3be06e9715@codesourcery.com> From: Arnd Bergmann Date: Mon, 26 Mar 2018 17:11:45 +0200 Message-ID: Subject: Re: [gnu-csky] [PATCH 00/19] C-SKY(csky) Linux Kernel Port Content-Type: text/plain; charset="UTF-8" Sender: linux-arch-owner@vger.kernel.org List-ID: To: Sandra Loosemore Cc: Guo Ren , linux-arch , Jason Cooper , Daniel Lezcano , Linux Kernel Mailing List , c-sky_gcc_upstream@c-sky.com, wbx@uclibc-ng.org, thomas.petazzoni@bootlin.com, gnu-csky@mentor.com, Thomas Gleixner Message-ID: <20180326151145.OxHmxVUISndB2fraQV_6URPaLiwx19NArsEsVa6eQrg@z> On Mon, Mar 26, 2018 at 5:06 PM, Sandra Loosemore 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