From: Arnd Bergmann <arnd@arndb.de>
To: Brian Cain <bcain@codeaurora.org>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sid Manning <sidneym@codeaurora.org>,
"open list:QUALCOMM HEXAGON..." <linux-hexagon@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: how can we test the hexagon port in mainline
Date: Wed, 23 Jun 2021 16:53:45 +0200 [thread overview]
Message-ID: <CAK8P3a28_0KJpcLRQrDhFk8-ndxmfk7-Q2_qcRRiYkyh-NNZUQ@mail.gmail.com> (raw)
In-Reply-To: <08df01d7683d$8f5b7b70$ae127250$@codeaurora.org>
On Wed, Jun 23, 2021 at 4:39 PM Brian Cain <bcain@codeaurora.org> wrote:
>
> > -----Original Message-----
> > From: Christoph Hellwig <hch@lst.de>
> ...
> >
> > Hi all,
> >
> > the oldest supported gcc version in mainline is gcc 4.9. But the only
> > hexagon crosscompiler I can find is the one Arnds website points to here:
> >
> > https://mirrors.edge.kernel.org/pub/tools/crosstool/
> >
> > which is a non-upstream gcc 4.6.1 port. How are we supposed to even
> > build test hexagon code?
>
> We have provided a clang-12-based toolchain here:
>
> https://codelinaro.jfrog.io/artifactory/codelinaro-qemu/2021-05-12/clang+llv
> m-12.0.0-cross-hexagon-unknown-linux-musl.tar.xz
How close is this to the mainline clang builds from https://apt.llvm.org/?
The last time we talked, there were still a couple of bugs that prevented
me from building an unmodified kernel with an unmodified clang toolchain,
but I think you planned to address those. Are any changes left that did
not make it into the 12.0 release?
> Could we update https://mirrors.edge.kernel.org/pub/tools/crosstool/ to
> point here?
I'm happy to edit the index page on
https://mirrors.edge.kernel.org/pub/tools/crosstool,
but could you provide a stable URL that will keep pointing to the latest version
in the future so I don't have to update it for each new build?
Arnd
next prev parent reply other threads:[~2021-06-23 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 14:18 how can we test the hexagon port in mainline Christoph Hellwig
2021-06-23 14:39 ` Brian Cain
2021-06-23 14:39 ` Brian Cain
2021-06-23 14:53 ` Arnd Bergmann [this message]
2021-06-23 15:15 ` Brian Cain
2021-06-23 15:17 ` 'Christoph Hellwig'
2021-06-23 15:35 ` Arnd Bergmann
2021-06-24 4:06 ` Nathan Chancellor
2021-07-07 14:10 ` Christoph Hellwig
2021-07-07 17:42 ` Nathan Chancellor
2021-07-08 5:27 ` Christoph Hellwig
2021-07-08 17:54 ` Nick Desaulniers
2021-07-08 18:35 ` Brian Cain
2021-07-08 18:35 ` Brian Cain
2021-07-08 19:08 ` Nick Desaulniers
2021-06-23 15:10 ` 'Christoph Hellwig'
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=CAK8P3a28_0KJpcLRQrDhFk8-ndxmfk7-Q2_qcRRiYkyh-NNZUQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=bcain@codeaurora.org \
--cc=hch@lst.de \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sidneym@codeaurora.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.