From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Joel Stanley <joel@jms.id.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Jinsong Ji <jji@us.ibm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [v2] raid6/ppc: Fix build for clang
Date: Sat, 22 Dec 2018 20:55:01 +1100 (AEDT) [thread overview]
Message-ID: <43MLT217xxz9sPZ@ozlabs.org> (raw)
In-Reply-To: <20181102004455.10157-1-joel@jms.id.au>
On Fri, 2018-11-02 at 00:44:55 UTC, Joel Stanley wrote:
> We cannot build these files with clang as it does not allow altivec
> instructions in assembly when -msoft-float is passed.
>
> Jinsong Ji <jji@us.ibm.com> wrote:
> > We currently disable Altivec/VSX support when enabling soft-float. So
> > any usage of vector builtins will break.
> >
> > Enable Altivec/VSX with soft-float may need quite some clean up work, so
> > I guess this is currently a limitation.
> >
> > Removing -msoft-float will make it work (and we are lucky that no
> > floating point instructions will be generated as well).
>
> This is a workaround until the issue is resolved in clang.
>
> Link: https://bugs.llvm.org/show_bug.cgi?id=31177
> Link: https://github.com/ClangBuiltLinux/linux/issues/239
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/e213574a449f7a57d4202c1869bbc7
cheers
prev parent reply other threads:[~2018-12-22 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 0:44 [PATCH v2] raid6/ppc: Fix build for clang Joel Stanley
2018-11-02 17:34 ` Nick Desaulniers
2018-12-03 10:24 ` Joel Stanley
2018-12-03 18:45 ` Nick Desaulniers
2018-12-03 22:13 ` Joel Stanley
2018-12-03 22:55 ` Nick Desaulniers
2018-12-03 23:24 ` Segher Boessenkool
2018-12-22 9:55 ` Michael Ellerman [this message]
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=43MLT217xxz9sPZ@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=jji@us.ibm.com \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ndesaulniers@google.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 NNTP newsgroup(s).