From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"mmarek@suse.cz" <mmarek@suse.cz>
Subject: Re: Build regressions/improvements in v4.9-rc1
Date: Thu, 27 Oct 2016 11:11:18 +0200 [thread overview]
Message-ID: <20161027111118.5c585d51@free-electrons.com> (raw)
In-Reply-To: <1477559240.2561.8.camel@synopsys.com>
Hello,
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.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-27 14:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 7:21 Build regressions/improvements in v4.9-rc1 Geert Uytterhoeven
2016-10-17 7:34 ` Geert Uytterhoeven
2016-10-17 16:59 ` Vineet Gupta
2016-10-17 21:02 ` Arnd Bergmann
2016-10-17 22:37 ` Vineet Gupta
2016-10-19 11:50 ` Michael Ellerman
2016-10-19 12:23 ` Alexey Brodkin
2016-10-19 20:32 ` Thomas Petazzoni
2016-10-26 23:56 ` Michael Ellerman
2016-10-27 7:07 ` Thomas Petazzoni
2016-10-27 9:07 ` Alexey Brodkin
2016-10-27 9:11 ` Thomas Petazzoni [this message]
2016-10-27 9:24 ` Geert Uytterhoeven
2016-10-27 9:39 ` Alexey Brodkin
2016-10-27 17:21 ` Vineet Gupta
2016-10-28 10:42 ` Arnd Bergmann
2016-10-27 9:32 ` Arnd Bergmann
2016-10-27 10:04 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161027111118.5c585d51@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox