From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "anders.roxell@linaro.org" <anders.roxell@linaro.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
Linux Kernel Functional Testing <lkft@linaro.org>,
"pali@kernel.org" <pali@kernel.org>
Subject: Re: [PATCH 1/2] powerpc/64: Set default CPU in Kconfig
Date: Wed, 1 Feb 2023 11:41:10 +0000 [thread overview]
Message-ID: <04b55866-aa17-f500-855a-7d4fb4bbaacf@csgroup.eu> (raw)
In-Reply-To: <20230201113155.18113-1-naresh.kamboju@linaro.org>
Le 01/02/2023 à 12:31, Naresh Kamboju a écrit :
> Following build regression started from next-20230131.
>
> Regressions found on powerpc:
>
> build/clang-nightly-tqm8xx_defconfig
> build/clang-nightly-ppc64e_defconfig
>
>
> make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0 tqm8xx_defconfig
> make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0
>
> error: unknown target CPU '860'
> note: valid target CPU values are: generic, 440, 450, 601, 602, 603, 603e, 603ev, 604, 604e, 620, 630, g3, 7400, g4, 7450, g4+, 750, 8548, 970, g5, a2, e500, e500mc, e5500, power3, pwr3, power4, pwr4, power5, pwr5, power5x, pwr5x, power6, pwr6, power6x, pwr6x, power7, pwr7, power8, pwr8, power9, pwr9, power10, pwr10, powerpc, ppc, ppc32, powerpc64, ppc64, powerpc64le, ppc64le, future
> make[2]: *** [/builds/linux/scripts/Makefile.build:114: scripts/mod/devicetable-offsets.s] Error 1
> error: unknown target CPU '860'
> note: valid target CPU values are: generic, 440, 450, 601, 602, 603, 603e, 603ev, 604, 604e, 620, 630, g3, 7400, g4, 7450, g4+, 750, 8548, 970, g5, a2, e500, e500mc, e5500, power3, pwr3, power4, pwr4, power5, pwr5, power5x, pwr5x, power6, pwr6, power6x, pwr6x, power7, pwr7, power8, pwr8, power9, pwr9, power10, pwr10, powerpc, ppc, ppc32, powerpc64, ppc64, powerpc64le, ppc64le, future
> make[2]: *** [/builds/linux/scripts/Makefile.build:252: scripts/mod/empty.o] Error 1
On GCC, the possible values are:
ppc-linux-gcc: note : valid arguments to ‘-mcpu=’ are: 401 403 405 405fp
440 440fp 464 464fp 476 476fp 505 601 602 603 603e 604 604e 620 630 740
7400 7450 750 801 821 823 8540 8548 860 970 G3 G4 G5 a2 cell e300c2
e300c3 e500mc e500mc64 e5500 e6500 ec603e native power3 power4 power5
power5+ power6 power6x power7 power8 powerpc powerpc64 powerpc64le rs64
titan
How do you tell CLANG that you are building for powerpc 8xx ?
>
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230201/testrun/14479384/suite/build/test/clang-nightly-tqm8xx_defconfig/history/
>
> The bisection pointed to this commit,
> 45f7091aac35 ("powerpc/64: Set default CPU in Kconfig")
>
> --
> Linaro LKFT
> https://lkft.linaro.org
next prev parent reply other threads:[~2023-02-01 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 7:38 [PATCH 1/2] powerpc/64: Set default CPU in Kconfig Christophe Leroy
2023-01-25 7:39 ` [PATCH 2/2] powerpc/boot: Don't always pass -mcpu=powerpc when building 32-bit uImage Christophe Leroy
2023-02-01 11:31 ` [PATCH 1/2] powerpc/64: Set default CPU in Kconfig Naresh Kamboju
2023-02-01 11:41 ` Christophe Leroy [this message]
2023-02-01 17:29 ` Nick Desaulniers
2023-02-03 17:58 ` Pali Rohár
2023-02-03 18:22 ` Christophe Leroy
2023-02-05 0:46 ` 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=04b55866-aa17-f500-855a-7d4fb4bbaacf@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkft@linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=npiggin@gmail.com \
--cc=pali@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox