From: Anton Blanchard <anton@samba.org>
To: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
behanw@converseincode.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/6] Build ppc64le kernel with llvm/clang
Date: Tue, 26 May 2015 08:53:24 +1000 [thread overview]
Message-ID: <1432594410-31198-1-git-send-email-anton@samba.org> (raw)
Now that Michael has fixed the 32 bit VDSO issue in his next branch, there are only
a few remaining things left to get the ppc64le kernel building with clang.
The last patch is a hack to workaround some generic Makefile issues. Hopefully the
relevant bits of the LLVMLinux tree will get merged upstream to fix them.
Anton Blanchard (6):
powerpc: Fix duplicate const clang warning in user access code
powerpc: Only use -mabi=altivec if toolchain supports it
powerpc: Only use -mtraceback=no, -mno-string and -msoft-float if
toolchain supports it
powerpc: Don't use -mno-strict-align on clang
powerpc: Don't use gcc specific options on clang
llvm: A few Makefile hacks
Makefile | 5 +++++
arch/powerpc/Makefile | 14 ++++++++++----
arch/powerpc/include/asm/uaccess.h | 8 ++++----
arch/powerpc/lib/Makefile | 2 +-
lib/raid6/Makefile | 2 +-
5 files changed, 21 insertions(+), 10 deletions(-)
--
2.1.4
next reply other threads:[~2015-05-25 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 22:53 Anton Blanchard [this message]
2015-05-25 22:53 ` [PATCH 1/6] powerpc: Fix duplicate const clang warning in user access code Anton Blanchard
2015-05-25 22:53 ` [PATCH 2/6] powerpc: Only use -mabi=altivec if toolchain supports it Anton Blanchard
2015-05-25 22:53 ` [PATCH 3/6] powerpc: Only use -mtraceback=no, -mno-string and -msoft-float " Anton Blanchard
2015-05-25 22:53 ` [PATCH 4/6] powerpc: Don't use -mno-strict-align on clang Anton Blanchard
2015-05-25 22:53 ` [PATCH 5/6] powerpc: Don't use gcc specific options " Anton Blanchard
2015-05-25 22:53 ` [PATCH 6/6] llvm: A few Makefile hacks Anton Blanchard
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=1432594410-31198-1-git-send-email-anton@samba.org \
--to=anton@samba.org \
--cc=behanw@converseincode.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).