From: Arnd Bergmann <arnd@arndb.de>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:QUALCOMM HEXAGON..." <linux-hexagon@vger.kernel.org>,
Chen Liqin <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Guenter Roeck <linux@roeck-us.net>,
Al Viro <viro@zeniv.linux.org.uk>,
James Hogan <jhogan@kernel.org>,
"open list:METAG ARCHITECTURE" <linux-metag@vger.kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Stafford Horne <shorne@gmail.com>,
openrisc@lists.librecores.org,
David Howells <dhowells@redhat.com>
Subject: Re: Removing architectures without upstream gcc support
Date: Wed, 28 Feb 2018 09:37:09 +0100 [thread overview]
Message-ID: <CAK8P3a13VDiH8+NG00p5oM2j5KMNU3JnCUurFn6EdJgztZsKHg@mail.gmail.com> (raw)
In-Reply-To: <20180228020631.GB3780@codeaurora.org>
On Wed, Feb 28, 2018 at 3:06 AM, Richard Kuo <rkuo@codeaurora.org> wrote:
> On Thu, Feb 22, 2018 at 11:43:10PM +0100, Arnd Bergmann wrote:
>> - How do I build an llvm based toolchain for Hexagon? Do I need patches
>> on top of the llvm-6 release branch? Where can I find the corresponding
>> binutils-2.30 sources?
>
> Just to follow up on this, the closest thing right now to compile the kernel
> for Hexagon is the toolchain included with the Hexagon SDK. However, the
> linker will fail because of something in the kernel build process that
> I think produces empty sections, which that linker can't handle. A newer
> linker can handle it, but that's not scheduled to be released until much later
> this year.
>
> That's actually the closest option currently. I tried the upstream source
> but it seems to lack some specific patches to support kernel compilation,
> so I will need to chase those down.
Thanks for trying it out. Can you point me to the sources? I tried downloading
a Hexagon SDK when I first looked at it, but only got a huge chunk of binary
java files and gave up before finding the llvm patches.
Arnd
next prev parent reply other threads:[~2018-02-28 8:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 15:45 Removing architectures without upstream gcc support Arnd Bergmann
2018-02-22 16:02 ` Christoph Hellwig
2018-02-22 16:19 ` Arnd Bergmann
2018-02-22 17:14 ` Max Filippov
2018-02-22 18:04 ` Christoph Hellwig
2018-02-23 11:37 ` Arnd Bergmann
2018-02-28 8:59 ` Florian Weimer
2018-02-22 16:07 ` Lennox Wu
2018-02-22 16:28 ` James Hogan
2018-02-22 16:34 ` Arnd Bergmann
2018-02-22 19:17 ` Richard Kuo
2018-02-22 22:43 ` Arnd Bergmann
2018-02-23 17:15 ` Richard Kuo
2018-02-28 2:06 ` Richard Kuo
2018-02-28 8:37 ` Arnd Bergmann [this message]
2018-03-03 1:43 ` Richard Kuo
2018-02-22 23:48 ` Guenter Roeck
2018-02-23 10:32 ` Arnd Bergmann
2018-02-23 12:09 ` Andy Shevchenko
2018-02-23 12:20 ` Arnd Bergmann
2018-02-23 14:32 ` Guenter Roeck
2018-02-23 15:43 ` Alan Cox
2018-02-23 17:10 ` Guenter Roeck
2018-02-23 18:19 ` Al Viro
2018-02-23 19:32 ` James Bottomley
2018-02-23 21:34 ` Adam Borowski
2018-02-24 4:04 ` Guenter Roeck
2018-02-24 21:55 ` Guenter Roeck
2018-02-25 19:39 ` [OpenRISC] " Richard Henderson
2018-02-23 23:49 ` Greg Ungerer
2018-02-25 20:28 ` Alan Cox
2018-02-25 22:50 ` Pavel Machek
2018-02-24 0:15 ` Florian Fainelli
2018-02-26 8:26 ` Arnd Bergmann
2018-02-26 22:11 ` Eric W. Biederman
2018-02-25 15:43 ` [OpenRISC] " Philipp Wagner
2018-02-26 8:00 ` Arnd Bergmann
2018-02-26 12:10 ` Philipp Wagner
2018-02-26 15:24 ` whitequark
2018-03-09 14:00 ` Xuetao Guan
2018-03-09 14:18 Guan Xuetao
2018-03-09 14:33 ` Arnd Bergmann
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=CAK8P3a13VDiH8+NG00p5oM2j5KMNU3JnCUurFn6EdJgztZsKHg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=jhogan@kernel.org \
--cc=jonas@southpole.se \
--cc=lennox.wu@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--cc=openrisc@lists.librecores.org \
--cc=rkuo@codeaurora.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).