From: "Brian Cain" <bcain@codeaurora.org>
To: "'Arnd Bergmann'" <arnd@kernel.org>,
"'Randy Dunlap'" <rdunlap@infradead.org>
Cc: "'Nick Desaulniers'" <ndesaulniers@google.com>,
"'open list:QUALCOMM HEXAGON...'" <linux-hexagon@vger.kernel.org>,
"'clang-built-linux'" <clang-built-linux@googlegroups.com>,
"'linux-arch'" <linux-arch@vger.kernel.org>,
"'Guenter Roeck'" <linux@roeck-us.net>
Subject: RE: ARCH=hexagon unsupported?
Date: Fri, 23 Apr 2021 14:31:11 -0500 [thread overview]
Message-ID: <026d01d73877$386a1920$a93e4b60$@codeaurora.org> (raw)
In-Reply-To: <CAK8P3a0ttLxzP0J-mocxB2TkfEYJYj37TdW=uM65fB4giC_qeg@mail.gmail.com>
> -----Original Message-----
> From: Arnd Bergmann <arnd@kernel.org>
...
> > There is no current gcc C compiler in the 3 locations that I know of to look.
> > The one I tried is v4.6 and it is too old to work with current makefiles.
>
> Correct, as I understand it , work on gcc was stopped after the 4.6 release
> and any testing internally to Qualcomm was done using a patched clang. A
> few years ago this was said to be (almost?) entirely upstream, but as Nick
> points out it has never been possible to build an upstream hexagon kernel
> with an upstream clang.
The critical missing component for a conventional build are implementations for compiler-emitted calls to builtins like __hexagon_memcpy_likely_aligned_min32bytes_mult8bytes, __hexagon_modsi3 -- these are available in the toolchain libraries (LIBGCC=libclang_rt.builtins-hexagon.a) but not in the kernel. This is easy to mitigate and yet disappointing that I did not do so before. I will do it.
There is a hexagon cross toolchain used for testing QEMU (userspace) guest code test cases. This same toolchain can be used to build the kernel. I will share a reference to that toolchain, standby.
-Brian
next prev parent reply other threads:[~2021-04-23 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 22:12 ARCH=hexagon unsupported? Nick Desaulniers
2021-04-23 9:36 ` Arnd Bergmann
2021-04-23 17:43 ` Randy Dunlap
2021-04-23 18:17 ` Arnd Bergmann
2021-04-23 18:26 ` Miguel Ojeda
2021-04-23 19:31 ` Brian Cain [this message]
2021-04-23 20:26 ` Brian Cain
2021-04-23 21:47 ` Randy Dunlap
2021-04-23 22:25 ` Brian Cain
2021-04-23 22:26 ` Randy Dunlap
2021-05-19 15:28 ` Brian Cain
2021-04-23 18:35 ` Brian Cain
2021-04-23 21:40 ` Nick Desaulniers
2021-04-26 13:13 ` Brian Cain
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='026d01d73877$386a1920$a93e4b60$@codeaurora.org' \
--to=bcain@codeaurora.org \
--cc=arnd@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ndesaulniers@google.com \
--cc=rdunlap@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;
as well as URLs for NNTP newsgroup(s).