From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nathan Chancellor <nathan@kernel.org>
Cc: npiggin@gmail.com, christophe.leroy@csgroup.eu,
aneesh.kumar@kernel.org, naveen.n.rao@linux.ibm.com,
morbo@google.com, justinstitt@google.com,
linuxppc-dev@lists.ozlabs.org, patches@lists.linux.dev,
llvm@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH] powerpc: xor_vmx: Add '-mhard-float' to CFLAGS
Date: Thu, 14 Mar 2024 00:19:43 +1100 [thread overview]
Message-ID: <171033598345.517247.13813107624896171770.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20240127-ppc-xor_vmx-drop-msoft-float-v1-1-f24140e81376@kernel.org>
On Sat, 27 Jan 2024 11:07:43 -0700, Nathan Chancellor wrote:
> arch/powerpc/lib/xor_vmx.o is built with '-msoft-float' (from the main
> powerpc Makefile) and '-maltivec' (from its CFLAGS), which causes an
> error when building with clang after a recent change in main:
>
> error: option '-msoft-float' cannot be specified with '-maltivec'
> make[6]: *** [scripts/Makefile.build:243: arch/powerpc/lib/xor_vmx.o] Error 1
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: xor_vmx: Add '-mhard-float' to CFLAGS
https://git.kernel.org/powerpc/c/35f20786c481d5ced9283ff42de5c69b65e5ed13
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nathan Chancellor <nathan@kernel.org>
Cc: llvm@lists.linux.dev, patches@lists.linux.dev,
aneesh.kumar@kernel.org, npiggin@gmail.com,
justinstitt@google.com, naveen.n.rao@linux.ibm.com,
stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
morbo@google.com
Subject: Re: [PATCH] powerpc: xor_vmx: Add '-mhard-float' to CFLAGS
Date: Thu, 14 Mar 2024 00:19:43 +1100 [thread overview]
Message-ID: <171033598345.517247.13813107624896171770.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20240127-ppc-xor_vmx-drop-msoft-float-v1-1-f24140e81376@kernel.org>
On Sat, 27 Jan 2024 11:07:43 -0700, Nathan Chancellor wrote:
> arch/powerpc/lib/xor_vmx.o is built with '-msoft-float' (from the main
> powerpc Makefile) and '-maltivec' (from its CFLAGS), which causes an
> error when building with clang after a recent change in main:
>
> error: option '-msoft-float' cannot be specified with '-maltivec'
> make[6]: *** [scripts/Makefile.build:243: arch/powerpc/lib/xor_vmx.o] Error 1
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: xor_vmx: Add '-mhard-float' to CFLAGS
https://git.kernel.org/powerpc/c/35f20786c481d5ced9283ff42de5c69b65e5ed13
cheers
next prev parent reply other threads:[~2024-03-13 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 18:07 [PATCH] powerpc: xor_vmx: Add '-mhard-float' to CFLAGS Nathan Chancellor
2024-01-27 18:07 ` Nathan Chancellor
2024-03-05 22:43 ` Nathan Chancellor
2024-03-05 22:43 ` Nathan Chancellor
2024-03-06 1:01 ` Michael Ellerman
2024-03-06 1:01 ` Michael Ellerman
2024-03-06 16:48 ` Nathan Chancellor
2024-03-06 16:48 ` Nathan Chancellor
2024-03-13 13:19 ` Michael Ellerman [this message]
2024-03-13 13:19 ` Michael Ellerman
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=171033598345.517247.13813107624896171770.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=justinstitt@google.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=patches@lists.linux.dev \
--cc=stable@vger.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.