From: Nathan Chancellor <natechancellor@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
clang-built-linux@googlegroups.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-5.3-4 tag
Date: Sat, 10 Aug 2019 15:42:06 -0700 [thread overview]
Message-ID: <20190810224206.GA56490@archlinux-threadripper> (raw)
In-Reply-To: <CAHk-=whnEp5+EM53MaT-3ep1xjhrUqCdcfBfTF9YxByGsmDMRw@mail.gmail.com>
On Sat, Aug 10, 2019 at 10:21:01AM -0700, Linus Torvalds wrote:
> On Sat, Aug 10, 2019 at 3:11 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
> >
> > Just one fix, a revert of a commit that was meant to be a minor improvement to
> > some inline asm, but ended up having no real benefit with GCC and broke booting
> > 32-bit machines when using Clang.
>
> Pulled, but whenever there are possible subtle compiler issues I get
> nervous, and wonder if the problem was reported to the clang guys?
>
> In particular, if the kernel change was technically correct, maybe
> somebody else comes along in a few years and tries the same, and then
> it's another odd "why doesn't this work for person X when it works
> just fine for me"..
>
> Linus
It was.
https://github.com/ClangBuiltLinux/linux/issues/593
https://bugs.llvm.org/show_bug.cgi?id=42762
We're still waiting for input from the PowerPC backend maintainers as
that is most likely where this issue originates from.
Cheers,
Nathan
next prev parent reply other threads:[~2019-08-10 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 10:11 [GIT PULL] Please pull powerpc/linux.git powerpc-5.3-4 tag Michael Ellerman
2019-08-10 17:21 ` Linus Torvalds
2019-08-10 22:42 ` Nathan Chancellor [this message]
2019-08-10 22:51 ` Michael Ellerman
2019-08-10 19:30 ` pr-tracker-bot
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=20190810224206.GA56490@archlinux-threadripper \
--to=natechancellor@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).