From: Nicholas Piggin <npiggin@gmail.com>
To: Anton Blanchard <anton@ozlabs.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
benh@kernel.crashing.org, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/Makefiles: Fix clang/llvm build
Date: Tue, 21 Aug 2018 16:25:43 +1000 [thread overview]
Message-ID: <20180821162543.30e7f4b2@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20180821153839.6ce0a287@kryten>
On Tue, 21 Aug 2018 15:38:39 +1000
Anton Blanchard <anton@ozlabs.org> wrote:
> Hi Michael,
>
> > This breaks GCC 4.6.3 at least, which we still support:
> >
> > Assembler messages:
> > Error: invalid switch -mpower8
> > Error: unrecognized option -mpower8
> > ../scripts/mod/empty.c:1:0: fatal error: error closing -: Broken
> > pipe
>
> Yuck. We have POWER8 instructions in our assembly code, and a toolchain
> that doesn't understand the -mpower8 flag, but has support for
> power8 instructions.
>
> This is what I see on clang with -mpower7:
>
> /tmp/sstep-2afa55.s:7584: Error: unrecognized opcode: `lbarx'
> /tmp/sstep-2afa55.s:7626: Error: unrecognized opcode: `stbcx.'
> /tmp/sstep-2afa55.s:8077: Error: unrecognized opcode: `lharx'
> /tmp/sstep-2afa55.s:8140: Error: unrecognized opcode: `stbcx.'
>
> Nick: any suggestions?
cpu-as-$(CONFIG_PPC_BOOK3S_64) += $(call as-option,-Wa$(comma)-mpower8,-Wa$(comma)-mpower4)
?
Thanks,
Nick
prev parent reply other threads:[~2018-08-21 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 1:02 [PATCH] powerpc/Makefiles: Fix clang/llvm build Anton Blanchard
2018-08-21 5:18 ` Michael Ellerman
2018-08-21 5:38 ` Anton Blanchard
2018-08-21 6:25 ` Nicholas Piggin [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=20180821162543.30e7f4b2@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=anton@ozlabs.org \
--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).