From: "Brian Cain" <bcain@codeaurora.org>
To: 'Christoph Hellwig' <hch@lst.de>, 'Arnd Bergmann' <arnd@arndb.de>
Cc: 'Linus Torvalds' <torvalds@linux-foundation.org>,
'Sid Manning' <sidneym@codeaurora.org>,
linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: how can we test the hexagon port in mainline
Date: Wed, 23 Jun 2021 09:39:21 -0500 [thread overview]
Message-ID: <08df01d7683d$8f5b7b70$ae127250$@codeaurora.org> (raw)
In-Reply-To: <20210623141854.GA32155@lst.de>
> -----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
Could we update https://mirrors.edge.kernel.org/pub/tools/crosstool/ to
point here?
-Brian
WARNING: multiple messages have this Message-ID (diff)
From: "Brian Cain" <bcain@codeaurora.org>
To: "'Christoph Hellwig'" <hch@lst.de>, "'Arnd Bergmann'" <arnd@arndb.de>
Cc: "'Linus Torvalds'" <torvalds@linux-foundation.org>,
"'Sid Manning'" <sidneym@codeaurora.org>,
<linux-hexagon@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: how can we test the hexagon port in mainline
Date: Wed, 23 Jun 2021 09:39:21 -0500 [thread overview]
Message-ID: <08df01d7683d$8f5b7b70$ae127250$@codeaurora.org> (raw)
In-Reply-To: <20210623141854.GA32155@lst.de>
> -----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
Could we update https://mirrors.edge.kernel.org/pub/tools/crosstool/ to
point here?
-Brian
next prev parent reply other threads:[~2021-06-23 14:39 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 [this message]
2021-06-23 14:39 ` Brian Cain
2021-06-23 14:53 ` Arnd Bergmann
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='08df01d7683d$8f5b7b70$ae127250$@codeaurora.org' \
--to=bcain@codeaurora.org \
--cc=arnd@arndb.de \
--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.