Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1008925imm; Mon, 21 May 2018 19:18:21 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrn4UDRSGgoVC8WJu7mtMZNWjATFrhg73Qy8AVN4NY77SxtIV+38TbrETt4VG2ageC4MA7q X-Received: by 2002:a17:902:8218:: with SMTP id x24-v6mr22733414pln.57.1526955501027; Mon, 21 May 2018 19:18:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526955500; cv=none; d=google.com; s=arc-20160816; b=eRXulYzF/08Cuh5ESApcJ48qQR0TEG3zqBx4k+oMWZ5lAAJsBxO/S4TkOacEam9ZpT t0+CkR2Ysz7t35A6sIhuZ05/B5b/EiVMBNsaKEkmBT4XUggqut/baFqmTgvnieueSSyu rApV5J1oVKqxPACIaGE2kDaykmZrhkSLvp/Uy/2/2JobMwa2Pp/PnY/wbAjO8VS5NDSH w4Yx8ZTwh1SbTwBVLbMZaq6N8AsxqSzLGqN87ikCdRby/aOVEpmSkG9vGIPJSzbhO3iW RzHkRNoTTgO6kKmoKmMB+unlP8Tx9V6p2KYsEajyuaaQ0g3KeoJ8bDP1F01s7IFq8vKN 0H0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=jFrOkpjDBQiiUIrs7mw5/q180HojLoFlRCmfULQmwHI=; b=WSyll+/hKDpEHhB2o62zmFnJmbbLbLtzBmlJYpuHaGDM5/eVbjFk3mVwrjPxwx0aQw nCO9qrs2ZnF5x6cwCWSeOVREdVm9O9e6tWELiZy6Q2Udmk7VPrqBHnWyj9A6MXAfqAZL qfd5tr044twHI/K2R3AGrmdNcJQAjer0bAbDhFOeOCVmvI2Bc9e71QMLvDgt6GQR51yz j0I2MZ+z2y6e24qTolnaZiS2yhsoZVZ4TVJ2+bF4aYdDdWeDzVbR5eTgeJpkP3B4Ls4v u0BnQBsMW/WpoIB7ExVngzwHJdg+zmXdIT/IfYxdo21oLGXLgs95+IjYRUDoy90tU3Qk XPpQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 8-v6si15725366plc.444.2018.05.21.19.17.54; Mon, 21 May 2018 19:18:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751813AbeEVCQD (ORCPT + 99 others); Mon, 21 May 2018 22:16:03 -0400 Received: from exmail.andestech.com ([59.124.169.137]:61454 "EHLO ATCSQR.andestech.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751177AbeEVCQA (ORCPT ); Mon, 21 May 2018 22:16:00 -0400 Received: from mail.andestech.com (atcpcs16.andestech.com [10.0.1.222]) by ATCSQR.andestech.com with ESMTP id w4M2HRIT030036; Tue, 22 May 2018 10:17:27 +0800 (GMT-8) (envelope-from vincentc@andestech.com) Received: from andestech.com (10.0.1.85) by ATCPCS16.andestech.com (10.0.1.222) with Microsoft SMTP Server id 14.3.123.3; Tue, 22 May 2018 10:15:20 +0800 Date: Tue, 22 May 2018 10:15:21 +0800 From: Vincent Chen To: Arnd Bergmann CC: Greentime Hu , Guenter Roeck , "linux-kernel@vger.kernel.org" , "Greentime Ying-Han Hu(?????????)" , "Alec I-Wei Wu(?????????)" , Chung-Ju Wu , "Kito Huang-Jia Cheng(?????????)" , Vincent Chen Subject: Re: nds32 build failures Message-ID: <20180522021521.GB23455@andestech.com> References: <4ccb747b-fb3b-18c8-8737-2cc02d7b1c34@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [10.0.1.85] X-DNSRBL: X-MAIL: ATCSQR.andestech.com w4M2HRIT030036 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 11, 2018 at 01:17:05PM +0800, Kito Cheng wrote: > Hi Arnd: > > I am GCC guy from Andes, we've missed the release schedule for GCC 8, > we didn't upstream the Linux support on time. > > Our plan is put our GCC 8 on github and continue commit rest patches > to upstream. > And we'll put our source on github after our internal testing done. > > Thanks. > Dear Arnd: The prebuilt nds32 toochain with gcc 8 is placed here https://github.com/vincentzwc/prebuilt-nds32-toolchain/releases The source code of each component for this toolchain is placed here. a. gcc: path: https://github.com/andestech/gcc.git branch: nds32-8.1.0-upstream b. binutils path: https://github.com/andestech/binutils.git branch: nds32-binutils-2.30-branch-open c. glibc path: https://github.com/andestech/glibc.git branch: nds32-glibc-2.27-v0 d. Linux path: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git branch: master This toolchain also can be manually generated by the following script https://github.com/andestech/build_script/blob/master/build_toolchain.sh We successfully generate a bootable kernel image with nds32 defconfig by this toolchain. However, we find a new compiler warning, Wstringop-overflow, when building arch/nds32/kernel/vdso.o. We have sent a patch to fix it. Best regards Vincent > On Fri, May 11, 2018 at 10:40 AM, Arnd Bergmann wrote: > > On Wed, Apr 18, 2018 at 3:19 AM, Greentime Hu wrote: > >> 2018-04-17 20:47 GMT+08:00 Arnd Bergmann : > >>> On Mon, Apr 16, 2018 at 11:06 AM, Greentime Hu wrote: > >>>> 2018-04-16 11:58 GMT+08:00 Guenter Roeck : > >>>> > >>>> This built failure is because the toolchain version you used is not > >>>> supported the latest intrinsic function/macro. > >>>> We are sending the latest patchset now and we expect the whole new > >>>> features will be supported in gcc8.0.0 and binutil2.31+. > >>>> > >>>> If you'd like to get these new features of toolchain, you may use the > >>>> github version. > >>>> This is the built-script repo. https://github.com/andestech/build_script.git > >>> > >>> I've taken the gcc-6.3 sources from there, and updated them to gcc-6.4.0 > >>> in order to build a nds32le-linux toolchain based on the same version as > >>> the other ones. > >>> > >>> Unfortunately neither the usual binutils-2.29.1 nor your binutils worked > >>> for me, but I eventually managed to get a build using the binutils-2.30 > >>> release. > >>> > >>> With this, I could build a mainline kernel with a couple of warnings, > >>> but an 'allmodconfig' build still failed. > >>> > >>> Guenter, can you try my binary from > >>> www.kernel.org/pub/tools/crosstool/files/bin/x86_64/6.4.0/x86_64-gcc-6.4.0-nolibc-nds32le-linux.tar.xz > >>> ? > >>> > >>> If that works for you, I'll update the front-page and remove the nds32-elf > >>> toolchains. > >>> > >>> Greentime, do you have a patch set for gcc-7.3 as well, or are 6.3 and 8.0 the > >>> only working compilers for nds32le-linux? > >>> > >> > >> Hi, all: > >> > >> I just discuss with our toolchain colleagues. We have only gcc6.3 and > >> gcc8.0 for nds32le-linux. > >> I have the ld segmentation fault issue too when building kernel with > >> 'allmodconfig'. We are dealing with it. > > > > I've tried building the mainline gcc-8.1 sources for nds32le-linux and > > still got a failure with those (building gcc), building a nds32le-elf gcc-8.1.0 > > worked fine, but that fails to build the vdso (no support for -fPIC), so > > it's again unusable for building kernels. Any other ideas? > > > > Arnd