From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Tri Vo <trong@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux@googlegroups.com,
Nathan Chancellor <natechancellor@gmail.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Disable big endian builds with clang
Date: Wed, 7 Aug 2019 15:14:29 +0100 [thread overview]
Message-ID: <20190807141429.GG54191@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190807135618.GF54191@lakrids.cambridge.arm.com>
On Wed, Aug 07, 2019 at 02:56:19PM +0100, Mark Rutland wrote:
> On Wed, Aug 07, 2019 at 02:05:27PM +0100, Mark Brown wrote:
> > On Wed, Aug 07, 2019 at 02:01:11PM +0100, Mark Rutland wrote:
> > > On Tue, Aug 06, 2019 at 07:39:18PM +0100, Mark Brown wrote:
> >
> > > Judging by the kernel log linked in a reply, this is with:
> >
> > > * clang version 8.0.1-svn359952-1~exp1~20190504004501.65 (branches/release_80)
> >
> > > Is that the llvm.org binary release, or a custom build of clang?
> >
> > It's from a llvm.org .deb.
> >
> > > * Linux 5.3.0-rc2-next-20190730
> >
> > > Could we previously build a BE kernel with clang? If so, what's the
> > > last working kernel?
> >
> > As far as I know this has been broken for as long as we tried building
> > and booting big endian kernels in clang. The compile works fine, it's
> > just that the resulting binary doesn't seem to be working so well.
>
> I've just had a go, and it works for me. Log below from a BE busybox,
> but I also have a BE buildroot filesystem working.
>
> For reference, I'm using:
>
> * Linux v5.3-rc3 defconfig
> * LLVM 8.0.0 (x86_64) from llvm.org
> * GCC 8.1.0 (x86_64) from kernel.org crosstool
>
> ... so I don't think we should blacklist this just yet, but we certainly
> need to better understand the issue you're seeing. I'll have a go with
> LLVM 8.0.1 in case there's a regression from 8.0.0 to 8.0.1.
FWIW, using LLVM 8.0.1 also works for me, everything else being
unchanged.
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-07 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 18:39 [PATCH] arm64: Disable big endian builds with clang Mark Brown
2019-08-06 21:25 ` Nick Desaulniers
2019-08-06 23:47 ` Nick Desaulniers
2019-08-07 12:38 ` Mark Brown
2019-08-07 14:41 ` Robin Murphy
2019-08-07 16:01 ` Mark Brown
2019-08-07 13:01 ` Mark Rutland
2019-08-07 13:05 ` Mark Brown
2019-08-07 13:56 ` Mark Rutland
2019-08-07 14:14 ` Mark Rutland [this message]
2019-08-07 15:29 ` Mark Brown
2019-08-07 15:43 ` Mark Rutland
2019-08-07 16:19 ` Mark Brown
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=20190807141429.GG54191@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=trong@google.com \
--cc=will@kernel.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.