Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942247AbcJ0PWp (ORCPT ); Thu, 27 Oct 2016 11:22:45 -0400 Received: from mail-oi0-f41.google.com ([209.85.218.41]:36240 "EHLO mail-oi0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935082AbcJ0PWo (ORCPT ); Thu, 27 Oct 2016 11:22:44 -0400 MIME-Version: 1.0 In-Reply-To: <20161027111118.5c585d51@free-electrons.com> References: <1476688913-15648-1-git-send-email-geert@linux-m68k.org> <00b16c44-79b8-43b8-6516-13c8bb92eb03@synopsys.com> <5541266.ySlPfDOezF@wuerfel> <9a0f80b3-adb3-36de-d59f-885ac29ea2e6@synopsys.com> <87inso4kxb.fsf@concordia.ellerman.id.au> <1476879762.26312.12.camel@synopsys.com> <87shriwtpp.fsf@concordia.ellerman.id.au> <20161027090722.3ba2badc@free-electrons.com> <1477559240.2561.8.camel@synopsys.com> <20161027111118.5c585d51@free-electrons.com> From: Geert Uytterhoeven Date: Thu, 27 Oct 2016 11:24:07 +0200 X-Google-Sender-Auth: _tyTbaFeVqX2Nu3EeHEOWOY4DXg Message-ID: Subject: Re: Build regressions/improvements in v4.9-rc1 To: Thomas Petazzoni Cc: Alexey Brodkin , "mpe@ellerman.id.au" , "linux-snps-arc@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "peterz@infradead.org" , "Vineet.Gupta1@synopsys.com" , "arnd@arndb.de" , "mmarek@suse.cz" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2535 Lines: 57 On Thu, Oct 27, 2016 at 11:11 AM, Thomas Petazzoni wrote: > On Thu, 27 Oct 2016 09:07:55 +0000, Alexey Brodkin wrote: > >> > axs101 is using a 770 core, while the toolchain is built for the HS38 >> > core. I'm somewhat surprised that a single ARC toolchain cannot produce >> > code for both 770 and HS38, but it seems to be the case. >> > >> > So you need a separate toolchain for ARC770. >> >> Indeed axs101 uses ARC770 core which is ARCv1 AKA ARCompact ISA while >> axs103 sports the same base-board but CPU daughter-card contains ARC HS38 core >> which has ARCv2 ISA (binary incompatible with ARCompact). >> >> Essentially both gcc and binutils will happily build for both architectures given >> proper options were passed on the command line. But Linux kernel gets linked with >> pre-built libgcc (it is a part of toolchain). And so it all boils down to a requirement >> to have multilibbed uClibc toolchain. Which we don't have. > > Interesting. Why is libgcc linked with the kernel on ARC? I don't think > that's the case on other architectures: the kernel is freestanding and > provides everything that it needs without relying on the compiler > runtime. ARC is not the only one: $ git grep print-libgcc-file-name arch/arc/Makefile:LIBGCC := $(shell $(CC) $(cflags-y) --print-libgcc-file-name) arch/h8300/boot/compressed/Makefile:LIBGCC := $(shell $(CROSS-COMPILE)$(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) arch/hexagon/Makefile:LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) arch/m32r/Makefile:LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) arch/nios2/Makefile:LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) $(KCFLAGS) -print-libgcc-file-name) arch/openrisc/Makefile:LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) arch/parisc/Makefile:LIBGCC = $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) arch/tile/Makefile: $(shell $(CC) $(KBUILD_CFLAGS) $(KCFLAGS) -print-libgcc-file-name) arch/xtensa/Makefile:LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) arch/xtensa/boot/boot-redboot/Makefile:LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds