From: Michael Ellerman <mpe@ellerman.id.au> Date: 2020-11-16 12:38:22
Currently a build with CONFIG_E200=y will fail with:
Error: invalid switch -me200
Error: unrecognized option -me200
Upstream binutils has never supported an -me200 option. Presumably it
was supported at some point by either a fork or Freescale internal
binutils.
We can't support code that we can't even build test, so drop the
addition of -me200 to the build flags, so we can at least build with
CONFIG_E200=y.
Reported-by: Németh Márton <redacted>
Reported-by: kernel test robot <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
More discussion: https://lore.kernel.org/lkml/202011131146.g8dPLQDD-lkp@intel.com
---
arch/powerpc/Makefile | 1 -
1 file changed, 1 deletion(-)
@@ -248,7 +248,6 @@ KBUILD_CFLAGS += $(call cc-option,-mno-string)cpu-as-$(CONFIG_40x)+=-Wa,-m405cpu-as-$(CONFIG_44x)+=-Wa,-m440cpu-as-$(CONFIG_ALTIVEC)+=$(callas-option,-Wa$(comma)-maltivec)-cpu-as-$(CONFIG_E200)+=-Wa,-me200cpu-as-$(CONFIG_E500)+=-Wa,-me500# When using '-many -mpower4' gas will first try and find a matching power4
From: Scott Wood <oss@buserror.net> Date: 2020-11-16 20:44:38
On Mon, 2020-11-16 at 23:09 +1100, Michael Ellerman wrote:
Currently a build with CONFIG_E200=y will fail with:
Error: invalid switch -me200
Error: unrecognized option -me200
Upstream binutils has never supported an -me200 option. Presumably it
was supported at some point by either a fork or Freescale internal
binutils.
We can't support code that we can't even build test, so drop the
addition of -me200 to the build flags, so we can at least build with
CONFIG_E200=y.
Reported-by: Németh Márton <redacted>
Reported-by: kernel test robot <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
More discussion:
https://lore.kernel.org/lkml/202011131146.g8dPLQDD-lkp@intel.com
---
arch/powerpc/Makefile | 1 -
1 file changed, 1 deletion(-)
Acked-by: Scott Wood <oss@buserror.net>
I'd go further and remove E200 code entirely, unless someone with the hardware
can claim that it actually works. There doesn't appear to be any actual
platform support for an e200-based system. It seems to be a long-abandoned
work in progress.
-Scott
From: Nick Desaulniers <ndesaulniers@google.com> Date: 2020-11-16 23:35:05
On Mon, Nov 16, 2020 at 4:09 AM Michael Ellerman [off-list ref] wrote:
Currently a build with CONFIG_E200=y will fail with:
Error: invalid switch -me200
Error: unrecognized option -me200
Upstream binutils has never supported an -me200 option. Presumably it
was supported at some point by either a fork or Freescale internal
binutils.
We can't support code that we can't even build test, so drop the
addition of -me200 to the build flags, so we can at least build with
CONFIG_E200=y.
Reported-by: Németh Márton <redacted>
Reported-by: kernel test robot <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Thanks for the patch; this should make randconfig builds not pick this
non-buildable config.
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
@@ -248,7 +248,6 @@ KBUILD_CFLAGS += $(call cc-option,-mno-string)cpu-as-$(CONFIG_40x)+=-Wa,-m405cpu-as-$(CONFIG_44x)+=-Wa,-m440cpu-as-$(CONFIG_ALTIVEC)+=$(callas-option,-Wa$(comma)-maltivec)-cpu-as-$(CONFIG_E200)+=-Wa,-me200cpu-as-$(CONFIG_E500)+=-Wa,-me500# When using '-many -mpower4' gas will first try and find a matching power4--
From: Michael Ellerman <hidden> Date: 2020-11-17 23:15:42
On Mon, 16 Nov 2020 23:09:13 +1100, Michael Ellerman wrote:
Currently a build with CONFIG_E200=y will fail with:
Error: invalid switch -me200
Error: unrecognized option -me200
Upstream binutils has never supported an -me200 option. Presumably it
was supported at some point by either a fork or Freescale internal
binutils.
[...]