From: "Brian Cain" <bcain@codeaurora.org>
To: 'Randy Dunlap' <rdunlap@infradead.org>,
'Arnd Bergmann' <arnd@kernel.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>,
Sid Manning <sidneym@quicinc.com>
Subject: RE: ARCH=hexagon unsupported?
Date: Wed, 19 May 2021 10:28:07 -0500 [thread overview]
Message-ID: <06a701d74cc3$92bc59f0$b8350dd0$@codeaurora.org> (raw)
In-Reply-To: <42ab3057-3b43-7f98-6387-6e79761d2d3f@infradead.org>
> -----Original Message-----
> From: Randy Dunlap <rdunlap@infradead.org>
...
> > Randy,
> >
> > I 100% agree, I would prefer a tarball myself. I have been working with
> the team to produce the tarball and we haven't been able to deliver that yet.
> No good excuses here, only bad ones: somewhat tied up in process
> bureaucracy.
> >
> > I can share the recipe that was used to build the toolchain in the container.
> No Dockerfile required, just a shell script w/mostly cmake + make commands.
> All of the sources are public, but musl is a downstream-public repo because we
> haven't landed the hexagon support in upstream musl yet.
>
> Hi Brian,
> I can wait. :)
Randy, thanks for your patience. We don't quite have all the kinks worked out for a release process but I have worked with the Linaro team to produce a clang-based cross toolchain and we can share a link:
https://codelinaro.jfrog.io/artifactory/codelinaro-qemu/2021-05-12/clang+llvm-12.0.0-cross-hexagon-unknown-linux-musl.tar.xz
Contents:
- clang+llvm+lld+libunwind+libcxx+libcxxabi built from `llvmorg-12.0.0` release
- `qemu-hexagon` binary (scalar core only!) built from upstream github.com/qemu/qemu repo `15106f7dc3290ff3254611f265849a314a93eb0e`
- headers from linux kernel 5.6.18
- C library built from github.com/quic/musl commit aff74b395fbf59cd7e93b3691905aa1af6c0778c
- unabridged build details in https://github.com/quic/qemu/tree/d26f3843c794d9d9b17b637550dc3b5a2bacd837/quic/container
Once we're able to produce releases on a more regular basis we should be able to share a hexagon-linux-user QEMU that can do scalar+vector. And some time after that a sysemu-capable qemu.
Our process for this first run did not include a signature for the build tarball, and that is regrettable. It will be included next time around. I have produced the sha256 signature below (post hoc) of the tarball that I tested:
55c51e8289cc21e6779cfc3b18bb9ad02632fc52d3c3a91bf6fdb4c8f578c84c clang+llvm-12.0.0-cross-hexagon-unknown-linux-musl.tar.xz
-Brian
next prev parent reply other threads:[~2021-05-19 15:28 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
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 [this message]
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='06a701d74cc3$92bc59f0$b8350dd0$@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 \
--cc=sidneym@quicinc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).