clang: Powerpc: clang-nightly-maple_defconfig — FAIL

clang: Powerpc: clang-nightly-maple_defconfig — FAIL

[Naresh Kamboju]

[Please ignore if it is already reported]

Following two builds failed on stable-rc 6.1.34-rc1.

  - Powerpc: clang-nightly-maple_defconfig — FAIL
  - Powerpc: clang-nightly-cell_defconfig — FAIL

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

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 LD=powerpc64le-linux-gnu-ld

arch/powerpc/lib/copypage_power7.S: Assembler messages:
arch/powerpc/lib/copypage_power7.S:34: Error: junk at end of line: `0b01000'
arch/powerpc/lib/copypage_power7.S:35: Error: junk at end of line: `0b01010'
arch/powerpc/lib/copypage_power7.S:37: Error: junk at end of line: `0b01000'
arch/powerpc/lib/copypage_power7.S:38: Error: junk at end of line: `0b01010'
arch/powerpc/lib/copypage_power7.S:40: Error: junk at end of line: `0b01010'
clang: error: assembler command failed with exit code 1 (use -v to see
invocation)
make[4]: *** [scripts/Makefile.build:382:
arch/powerpc/lib/copypage_power7.o] Error 1
make[4]: Target 'arch/powerpc/lib/' not remade because of errors.
make[3]: *** [scripts/Makefile.build:500: arch/powerpc/lib] Error 2
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:2959: Error: junk at end of line: `0b01010'
arch/powerpc/kernel/exceptions-64s.S:2979: Error: junk at end of line: `0b01010'
arch/powerpc/kernel/exceptions-64s.S:2994: Error: junk at end of line: `0b01010'
arch/powerpc/kernel/exceptions-64s.S:3012: Error: junk at end of line: `0b01010'
arch/powerpc/kernel/exceptions-64s.S:3032: Error: junk at end of line: `0b01010'
arch/powerpc/kernel/exceptions-64s.S:3079: Error: junk at end of line: `0b01010'
clang: error: assembler command failed with exit code 1 (use -v to see
invocation)
make[4]: *** [scripts/Makefile.build:382: arch/powerpc/kernel/head_64.o] Error 1
arch/powerpc/kernel/entry_64.S: Assembler messages:
arch/powerpc/kernel/entry_64.S:172: Error: junk at end of line: `0b01010'
clang: error: assembler command failed with exit code 1 (use -v to see
invocation)
make[4]: *** [scripts/Makefile.build:382:
arch/powerpc/kernel/entry_64.o] Error 1
make[4]: Target 'arch/powerpc/kernel/' not remade because of errors.
make[3]: *** [scripts/Makefile.build:500: arch/powerpc/kernel] Error 2
make[3]: Target 'arch/powerpc/' not remade because of errors.
make[2]: *** [scripts/Makefile.build:500: arch/powerpc] Error 2
make[2]: Target './' not remade because of errors.
make[1]: *** [Makefile:2012: .] Error 2
make[1]: Target '__all' not remade because of errors.
make: *** [Makefile:238: __sub-make] Error 2
make: Target '__all' not remade because of errors.



Links,
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.33-133-g08f336c8c68d/testrun/17475368/suite/build/test/clang-nightly-cell_defconfig/history/
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.33-133-g08f336c8c68d/testrun/17475373/suite/build/test/clang-nightly-maple_defconfig/history/


--
Linaro LKFT
https://lkft.linaro.org

Re: clang: Powerpc: clang-nightly-maple_defconfig — FAIL

[Nathan Chancellor]

Hi Naresh,

On Tue, Jun 13, 2023 at 12:10:30AM +0530, Naresh Kamboju wrote:
> [Please ignore if it is already reported]
> 
> Following two builds failed on stable-rc 6.1.34-rc1.
> 
>   - Powerpc: clang-nightly-maple_defconfig — FAIL
>   - Powerpc: clang-nightly-cell_defconfig — FAIL
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> 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 LD=powerpc64le-linux-gnu-ld
> 
> arch/powerpc/lib/copypage_power7.S: Assembler messages:
> arch/powerpc/lib/copypage_power7.S:34: Error: junk at end of line: `0b01000'
> arch/powerpc/lib/copypage_power7.S:35: Error: junk at end of line: `0b01010'
> arch/powerpc/lib/copypage_power7.S:37: Error: junk at end of line: `0b01000'
> arch/powerpc/lib/copypage_power7.S:38: Error: junk at end of line: `0b01010'
> arch/powerpc/lib/copypage_power7.S:40: Error: junk at end of line: `0b01010'
> clang: error: assembler command failed with exit code 1 (use -v to see
> invocation)
> make[4]: *** [scripts/Makefile.build:382:
> arch/powerpc/lib/copypage_power7.o] Error 1
> make[4]: Target 'arch/powerpc/lib/' not remade because of errors.
> make[3]: *** [scripts/Makefile.build:500: arch/powerpc/lib] Error 2
> arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> arch/powerpc/kernel/exceptions-64s.S:2959: Error: junk at end of line: `0b01010'
> arch/powerpc/kernel/exceptions-64s.S:2979: Error: junk at end of line: `0b01010'
> arch/powerpc/kernel/exceptions-64s.S:2994: Error: junk at end of line: `0b01010'
> arch/powerpc/kernel/exceptions-64s.S:3012: Error: junk at end of line: `0b01010'
> arch/powerpc/kernel/exceptions-64s.S:3032: Error: junk at end of line: `0b01010'
> arch/powerpc/kernel/exceptions-64s.S:3079: Error: junk at end of line: `0b01010'
> clang: error: assembler command failed with exit code 1 (use -v to see
> invocation)
> make[4]: *** [scripts/Makefile.build:382: arch/powerpc/kernel/head_64.o] Error 1
> arch/powerpc/kernel/entry_64.S: Assembler messages:
> arch/powerpc/kernel/entry_64.S:172: Error: junk at end of line: `0b01010'
> clang: error: assembler command failed with exit code 1 (use -v to see
> invocation)
> make[4]: *** [scripts/Makefile.build:382:
> arch/powerpc/kernel/entry_64.o] Error 1
> make[4]: Target 'arch/powerpc/kernel/' not remade because of errors.
> make[3]: *** [scripts/Makefile.build:500: arch/powerpc/kernel] Error 2
> make[3]: Target 'arch/powerpc/' not remade because of errors.
> make[2]: *** [scripts/Makefile.build:500: arch/powerpc] Error 2
> make[2]: Target './' not remade because of errors.
> make[1]: *** [Makefile:2012: .] Error 2
> make[1]: Target '__all' not remade because of errors.
> make: *** [Makefile:238: __sub-make] Error 2
> make: Target '__all' not remade because of errors.

As always, thanks for the report. This is an LLVM regression/change in
behavior caused by [1], which can break as-option and as-instr on
releases prior to commit d5c8d6e0fa61 ("kbuild: Update assembler calls
to use proper flags and language target"), as unsupported flags for the
current target ('-x') may be present (KBUILD_CFLAGS is used for these
tests instead of KBUILD_AFLAGS). Inside try-run, the macro behind
as-instr and as-option, I see

  clang-17: error: unsupported option '-mno-prefixed' for target 'powerpc64le-linux-gnu'
  clang-17: error: unsupported option '-mno-pcrel' for target 'powerpc64le-linux-gnu'
  clang-17: error: unsupported option '-mno-altivec' for target 'powerpc64le-linux-gnu'
  clang-17: error: unsupported option '-mno-vsx' for target 'powerpc64le-linux-gnu'
  clang-17: error: unsupported option '-mno-mma' for target 'powerpc64le-linux-gnu'
  clang-17: error: unsupported option '-mno-spe' for target 'powerpc64le-linux-gnu'

This has come up recently elsewhere in PowerPC, see
commit 2b694fc96fe3 ("powerpc/boot: Disable power10 features after
BOOTAFLAGS assignment"). While I think it is dubious that clang errors
on these flags for the assembler target, this is already fixed on the
Linux side by using KBUILD_AFLAGS for these make macros.

I am preparing a series of d5c8d6e0fa61 and its dependencies for 6.1 but
I want to do sufficient build testing first, which is currently running
for me. Would you be able to point your matrix to [2] to make sure
everything works properly with both GCC and LLVM? It is a work in
progress as the second patch in the stack needs a proper commit message
but it is the diff I expect to ship so that it all that matters.

[1]: https://github.com/llvm/llvm-project/commit/5548843d692a92a7840f14002debc3cebcb3cdc3
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git/log/?h=wip/b4/6-1-asssembler-target-llvm-17

Cheers,
Nathan

Re: clang: Powerpc: clang-nightly-maple_defconfig — FAIL

[Naresh Kamboju]

Hi Nathan,

On Tue, 13 Jun 2023 at 00:24, Nathan Chancellor <nathan@kernel.org> wrote:
>
> Hi Naresh,
>
> On Tue, Jun 13, 2023 at 12:10:30AM +0530, Naresh Kamboju wrote:
> > [Please ignore if it is already reported]
> >
> > Following two builds failed on stable-rc 6.1.34-rc1.
> >
> >   - Powerpc: clang-nightly-maple_defconfig — FAIL
> >   - Powerpc: clang-nightly-cell_defconfig — FAIL
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > 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 LD=powerpc64le-linux-gnu-ld
> >
> > arch/powerpc/lib/copypage_power7.S: Assembler messages:
> > arch/powerpc/lib/copypage_power7.S:34: Error: junk at end of line: `0b01000'
> > arch/powerpc/lib/copypage_power7.S:35: Error: junk at end of line: `0b01010'
> > arch/powerpc/lib/copypage_power7.S:37: Error: junk at end of line: `0b01000'
> > arch/powerpc/lib/copypage_power7.S:38: Error: junk at end of line: `0b01010'
> > arch/powerpc/lib/copypage_power7.S:40: Error: junk at end of line: `0b01010'
> > clang: error: assembler command failed with exit code 1 (use -v to see
> > invocation)
> > make[4]: *** [scripts/Makefile.build:382:
> > arch/powerpc/lib/copypage_power7.o] Error 1
> > make[4]: Target 'arch/powerpc/lib/' not remade because of errors.
> > make[3]: *** [scripts/Makefile.build:500: arch/powerpc/lib] Error 2
> > arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> > arch/powerpc/kernel/exceptions-64s.S:2959: Error: junk at end of line: `0b01010'
> > arch/powerpc/kernel/exceptions-64s.S:2979: Error: junk at end of line: `0b01010'
> > arch/powerpc/kernel/exceptions-64s.S:2994: Error: junk at end of line: `0b01010'
> > arch/powerpc/kernel/exceptions-64s.S:3012: Error: junk at end of line: `0b01010'
> > arch/powerpc/kernel/exceptions-64s.S:3032: Error: junk at end of line: `0b01010'
> > arch/powerpc/kernel/exceptions-64s.S:3079: Error: junk at end of line: `0b01010'
> > clang: error: assembler command failed with exit code 1 (use -v to see
> > invocation)
> > make[4]: *** [scripts/Makefile.build:382: arch/powerpc/kernel/head_64.o] Error 1
> > arch/powerpc/kernel/entry_64.S: Assembler messages:
> > arch/powerpc/kernel/entry_64.S:172: Error: junk at end of line: `0b01010'
> > clang: error: assembler command failed with exit code 1 (use -v to see
> > invocation)
> > make[4]: *** [scripts/Makefile.build:382:
> > arch/powerpc/kernel/entry_64.o] Error 1
> > make[4]: Target 'arch/powerpc/kernel/' not remade because of errors.
> > make[3]: *** [scripts/Makefile.build:500: arch/powerpc/kernel] Error 2
> > make[3]: Target 'arch/powerpc/' not remade because of errors.
> > make[2]: *** [scripts/Makefile.build:500: arch/powerpc] Error 2
> > make[2]: Target './' not remade because of errors.
> > make[1]: *** [Makefile:2012: .] Error 2
> > make[1]: Target '__all' not remade because of errors.
> > make: *** [Makefile:238: __sub-make] Error 2
> > make: Target '__all' not remade because of errors.
>
> As always, thanks for the report. This is an LLVM regression/change in
> behavior caused by [1], which can break as-option and as-instr on
> releases prior to commit d5c8d6e0fa61 ("kbuild: Update assembler calls
> to use proper flags and language target"), as unsupported flags for the
> current target ('-x') may be present (KBUILD_CFLAGS is used for these
> tests instead of KBUILD_AFLAGS). Inside try-run, the macro behind
> as-instr and as-option, I see
>
>   clang-17: error: unsupported option '-mno-prefixed' for target 'powerpc64le-linux-gnu'
>   clang-17: error: unsupported option '-mno-pcrel' for target 'powerpc64le-linux-gnu'
>   clang-17: error: unsupported option '-mno-altivec' for target 'powerpc64le-linux-gnu'
>   clang-17: error: unsupported option '-mno-vsx' for target 'powerpc64le-linux-gnu'
>   clang-17: error: unsupported option '-mno-mma' for target 'powerpc64le-linux-gnu'
>   clang-17: error: unsupported option '-mno-spe' for target 'powerpc64le-linux-gnu'
>
> This has come up recently elsewhere in PowerPC, see
> commit 2b694fc96fe3 ("powerpc/boot: Disable power10 features after
> BOOTAFLAGS assignment"). While I think it is dubious that clang errors
> on these flags for the assembler target, this is already fixed on the
> Linux side by using KBUILD_AFLAGS for these make macros.
>
> I am preparing a series of d5c8d6e0fa61 and its dependencies for 6.1 but
> I want to do sufficient build testing first, which is currently running
> for me. Would you be able to point your matrix to [2] to make sure
> everything works properly with both GCC and LLVM? It is a work in
> progress as the second patch in the stack needs a proper commit message
> but it is the diff I expect to ship so that it all that matters.

We'll start building [2] with GCC and LLVM by using tuxplans and
get back to you.

>
> [1]: https://github.com/llvm/llvm-project/commit/5548843d692a92a7840f14002debc3cebcb3cdc3
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git/log/?h=wip/b4/6-1-asssembler-target-llvm-17
>
> Cheers,
> Nathan

- Naresh

Re: clang: Powerpc: clang-nightly-maple_defconfig — FAIL

[Naresh Kamboju]

Hi Nathan,

On Tue, 13 Jun 2023 at 09:57, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Hi Nathan,
>
> On Tue, 13 Jun 2023 at 00:24, Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > Hi Naresh,
> >
> > On Tue, Jun 13, 2023 at 12:10:30AM +0530, Naresh Kamboju wrote:
> > > [Please ignore if it is already reported]
> > >
> > > Following two builds failed on stable-rc 6.1.34-rc1.
> > >
> > >   - Powerpc: clang-nightly-maple_defconfig — FAIL
> > >   - Powerpc: clang-nightly-cell_defconfig — FAIL
> > >

> > As always, thanks for the report. This is an LLVM regression/change in
> > behavior caused by [1], which can break as-option and as-instr on
> > releases prior to commit d5c8d6e0fa61 ("kbuild: Update assembler calls
> > to use proper flags and language target"), as unsupported flags for the
> > current target ('-x') may be present (KBUILD_CFLAGS is used for these
> > tests instead of KBUILD_AFLAGS). Inside try-run, the macro behind
> > as-instr and as-option, I see
> >
> >   clang-17: error: unsupported option '-mno-prefixed' for target 'powerpc64le-linux-gnu'
> >   clang-17: error: unsupported option '-mno-pcrel' for target 'powerpc64le-linux-gnu'
> >   clang-17: error: unsupported option '-mno-altivec' for target 'powerpc64le-linux-gnu'
> >   clang-17: error: unsupported option '-mno-vsx' for target 'powerpc64le-linux-gnu'
> >   clang-17: error: unsupported option '-mno-mma' for target 'powerpc64le-linux-gnu'
> >   clang-17: error: unsupported option '-mno-spe' for target 'powerpc64le-linux-gnu'
> >
> > This has come up recently elsewhere in PowerPC, see
> > commit 2b694fc96fe3 ("powerpc/boot: Disable power10 features after
> > BOOTAFLAGS assignment"). While I think it is dubious that clang errors
> > on these flags for the assembler target, this is already fixed on the
> > Linux side by using KBUILD_AFLAGS for these make macros.
> >
> > I am preparing a series of d5c8d6e0fa61 and its dependencies for 6.1 but
> > I want to do sufficient build testing first, which is currently running
> > for me. Would you be able to point your matrix to [2] to make sure
> > everything works properly with both GCC and LLVM? It is a work in
> > progress as the second patch in the stack needs a proper commit message
> > but it is the diff I expect to ship so that it all that matters.
>
> We'll start building [2] with GCC and LLVM by using tuxplans and
> get back to you.

LKFT has been configured to run GCC and LLVM in total 205 builds
and all the builds have passed on your tree / branch [2]. You can find
the list of builds including kselftest, perf, rcutorture, kunit, kmemleak
and many more combinations and architectures.

I request you to review the list of builds results and test results on
projects page [3] [4]. I do not find any regressions compared with
mainline master as sanity testing.

Do you think LKFT should build your tree / branch often ?
We are happy to test anytime.

Thanks Daniel and Anders for your work.

build_names: that got tested and all have passed.

  - clang-16-allnoconfig
  - clang-16-at91_dt_defconfig
  - clang-16-axm55xx_defconfig
  - clang-16-bcm2835_defconfig
  - clang-16-cell_defconfig
  - clang-16-clps711x_defconfig
  - clang-16-davinci_all_defconfig
  - clang-16-defconfig
  - clang-16-defconfig-40bc7ee5
  - clang-16-exynos_defconfig
  - clang-16-footbridge_defconfig
  - clang-16-imx_v4_v5_defconfig
  - clang-16-imx_v6_v7_defconfig
  - clang-16-integrator_defconfig
  - clang-16-keystone_defconfig
  - clang-16-lkftconfig
  - clang-16-lkftconfig-compat
  - clang-16-lkftconfig-kcsan
  - clang-16-lkftconfig-no-kselftest-frag
  - clang-16-lpc32xx_defconfig
  - clang-16-maple_defconfig
  - clang-16-mpc83xx_defconfig
  - clang-16-multi_v5_defconfig
  - clang-16-multi_v5_defconfig-65236a87
  - clang-16-mxs_defconfig
  - clang-16-nhk8815_defconfig
  - clang-16-omap1_defconfig
  - clang-16-omap2plus_defconfig
  - clang-16-orion5x_defconfig
  - clang-16-ppc64e_defconfig
  - clang-16-pxa910_defconfig
  - clang-16-s3c6400_defconfig
  - clang-16-s5pv210_defconfig
  - clang-16-sama5_defconfig
  - clang-16-shmobile_defconfig
  - clang-16-tinyconfig
  - clang-16-tqm8xx_defconfig
  - clang-16-u8500_defconfig
  - clang-16-vexpress_defconfig
  - clang-16-x86_64_defconfig
  - clang-nightly-allnoconfig
  - clang-nightly-at91_dt_defconfig
  - clang-nightly-axm55xx_defconfig
  - clang-nightly-bcm2835_defconfig
  - clang-nightly-cell_defconfig
  - clang-nightly-clps711x_defconfig
  - clang-nightly-davinci_all_defconfig
  - clang-nightly-defconfig
  - clang-nightly-defconfig-40bc7ee5
  - clang-nightly-exynos_defconfig
  - clang-nightly-footbridge_defconfig
  - clang-nightly-imx_v4_v5_defconfig
  - clang-nightly-imx_v6_v7_defconfig
  - clang-nightly-integrator_defconfig
  - clang-nightly-keystone_defconfig
  - clang-nightly-lkftconfig
  - clang-nightly-lpc32xx_defconfig
  - clang-nightly-maple_defconfig
  - clang-nightly-mpc83xx_defconfig
  - clang-nightly-multi_v5_defconfig
  - clang-nightly-multi_v5_defconfig-65236a87
  - clang-nightly-mxs_defconfig
  - clang-nightly-nhk8815_defconfig
  - clang-nightly-omap1_defconfig
  - clang-nightly-omap2plus_defconfig
  - clang-nightly-orion5x_defconfig
  - clang-nightly-ppc64e_defconfig
  - clang-nightly-pxa910_defconfig
  - clang-nightly-s3c6400_defconfig
  - clang-nightly-s5pv210_defconfig
  - clang-nightly-sama5_defconfig
  - clang-nightly-shmobile_defconfig
  - clang-nightly-tinyconfig
  - clang-nightly-tqm8xx_defconfig
  - clang-nightly-u8500_defconfig
  - clang-nightly-vexpress_defconfig
  - clang-nightly-x86_64_defconfig
  - gcc-11-allnoconfig
  - gcc-11-defconfig
  - gcc-11-dreamcast_defconfig
  - gcc-11-lkftconfig
  - gcc-11-lkftconfig-perf
  - gcc-11-microdev_defconfig
  - gcc-11-shx3_defconfig
  - gcc-11-tinyconfig
  - gcc-12-allnoconfig
  - gcc-12-ar7_defconfig
  - gcc-12-at91_dt_defconfig
  - gcc-12-ath79_defconfig
  - gcc-12-axm55xx_defconfig
  - gcc-12-bcm2835_defconfig
  - gcc-12-bcm47xx_defconfig
  - gcc-12-bcm63xx_defconfig
  - gcc-12-cavium_octeon_defconfig
  - gcc-12-cell_defconfig
  - gcc-12-clps711x_defconfig
  - gcc-12-davinci_all_defconfig
  - gcc-12-defconfig
  - gcc-12-defconfig-40bc7ee5
  - gcc-12-exynos_defconfig
  - gcc-12-footbridge_defconfig
  - gcc-12-imx_v4_v5_defconfig
  - gcc-12-imx_v6_v7_defconfig
  - gcc-12-integrator_defconfig
  - gcc-12-ixp4xx_defconfig
  - gcc-12-keystone_defconfig
  - gcc-12-lkftconfig
  - gcc-12-lkftconfig-64k_page_size
  - gcc-12-lkftconfig-armv8_features
  - gcc-12-lkftconfig-compat
  - gcc-12-lkftconfig-debug
  - gcc-12-lkftconfig-debug-kmemleak
  - gcc-12-lkftconfig-devicetree
  - gcc-12-lkftconfig-kasan
  - gcc-12-lkftconfig-kselftest
  - gcc-12-lkftconfig-kunit
  - gcc-12-lkftconfig-libgpiod
  - gcc-12-lkftconfig-no-kselftest-frag
  - gcc-12-lkftconfig-perf
  - gcc-12-lkftconfig-rcutorture
  - gcc-12-lpc32xx_defconfig
  - gcc-12-malta_defconfig
  - gcc-12-maple_defconfig
  - gcc-12-mpc83xx_defconfig
  - gcc-12-multi_v5_defconfig
  - gcc-12-multi_v5_defconfig-65236a87
  - gcc-12-mxs_defconfig
  - gcc-12-nhk8815_defconfig
  - gcc-12-omap1_defconfig
  - gcc-12-omap2plus_defconfig
  - gcc-12-orion5x_defconfig
  - gcc-12-ppc64e_defconfig
  - gcc-12-ppc6xx_defconfig
  - gcc-12-pxa910_defconfig
  - gcc-12-rt305x_defconfig
  - gcc-12-s3c6400_defconfig
  - gcc-12-s5pv210_defconfig
  - gcc-12-sama5_defconfig
  - gcc-12-shmobile_defconfig
  - gcc-12-tinyconfig
  - gcc-12-tqm8xx_defconfig
  - gcc-12-u8500_defconfig
  - gcc-12-vexpress_defconfig
  - gcc-8-allnoconfig
  - gcc-8-ar7_defconfig
  - gcc-8-at91_dt_defconfig
  - gcc-8-ath79_defconfig
  - gcc-8-axm55xx_defconfig
  - gcc-8-bcm2835_defconfig
  - gcc-8-bcm47xx_defconfig
  - gcc-8-bcm63xx_defconfig
  - gcc-8-cavium_octeon_defconfig
  - gcc-8-cell_defconfig
  - gcc-8-clps711x_defconfig
  - gcc-8-davinci_all_defconfig
  - gcc-8-defconfig
  - gcc-8-defconfig-40bc7ee5
  - gcc-8-defconfig-fe40093d
  - gcc-8-dreamcast_defconfig
  - gcc-8-exynos_defconfig
  - gcc-8-footbridge_defconfig
  - gcc-8-i386_defconfig
  - gcc-8-imx_v4_v5_defconfig
  - gcc-8-imx_v6_v7_defconfig
  - gcc-8-integrator_defconfig
  - gcc-8-ixp4xx_defconfig
  - gcc-8-keystone_defconfig
  - gcc-8-lpc32xx_defconfig
  - gcc-8-malta_defconfig
  - gcc-8-maple_defconfig
  - gcc-8-microdev_defconfig
  - gcc-8-mpc83xx_defconfig
  - gcc-8-multi_v5_defconfig
  - gcc-8-mxs_defconfig
  - gcc-8-nhk8815_defconfig
  - gcc-8-omap1_defconfig
  - gcc-8-omap2plus_defconfig
  - gcc-8-orion5x_defconfig
  - gcc-8-ppc64e_defconfig
  - gcc-8-ppc6xx_defconfig
  - gcc-8-pxa910_defconfig
  - gcc-8-rt305x_defconfig
  - gcc-8-s3c6400_defconfig
  - gcc-8-s5pv210_defconfig
  - gcc-8-sama5_defconfig
  - gcc-8-shmobile_defconfig
  - gcc-8-shx3_defconfig
  - gcc-8-tinyconfig
  - gcc-8-tqm8xx_defconfig
  - gcc-8-u8500_defconfig
  - gcc-8-vexpress_defconfig
  - gcc-8-x86_64_defconfig
  - gcc-9-allnoconfig
  - gcc-9-axs103_defconfig
  - gcc-9-defconfig
  - gcc-9-tinyconfig
  - gcc-9-vdk_hs38_smp_defconfig
  - rv32-clang-16-allnoconfig
  - rv32-clang-16-defconfig
  - rv32-clang-16-lkftconfig
  - rv32-clang-16-tinyconfig
  - rv32-clang-nightly-allnoconfig
  - rv32-clang-nightly-defconfig
  - rv32-clang-nightly-tinyconfig
  - rv32-gcc-11-lkftconfig


> > [1]: https://github.com/llvm/llvm-project/commit/5548843d692a92a7840f14002debc3cebcb3cdc3
> > [2]: https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git/log/?h=wip/b4/6-1-asssembler-target-llvm-17

[3] https://qa-reports.linaro.org/~anders.roxell/natan-6-1-asssembler-target-llvm-17/build/v6.1-6642-gb29a8d48035a/metadata/
[4] https://qa-reports.linaro.org/~anders.roxell/natan-6-1-asssembler-target-llvm-17/build/v6.1-6642-gb29a8d48035a/


> > Cheers,
> > Nathan


- Naresh

Re: clang: Powerpc: clang-nightly-maple_defconfig — FAIL

[Nathan Chancellor]

On Wed, Jun 14, 2023 at 07:43:45PM +0530, Naresh Kamboju wrote:
> Hi Nathan,
> 
> On Tue, 13 Jun 2023 at 09:57, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Hi Nathan,
> >
> > On Tue, 13 Jun 2023 at 00:24, Nathan Chancellor <nathan@kernel.org> wrote:
> > >
> > > Hi Naresh,
> > >
> > > On Tue, Jun 13, 2023 at 12:10:30AM +0530, Naresh Kamboju wrote:
> > > > [Please ignore if it is already reported]
> > > >
> > > > Following two builds failed on stable-rc 6.1.34-rc1.
> > > >
> > > >   - Powerpc: clang-nightly-maple_defconfig — FAIL
> > > >   - Powerpc: clang-nightly-cell_defconfig — FAIL
> > > >
> 
> > > As always, thanks for the report. This is an LLVM regression/change in
> > > behavior caused by [1], which can break as-option and as-instr on
> > > releases prior to commit d5c8d6e0fa61 ("kbuild: Update assembler calls
> > > to use proper flags and language target"), as unsupported flags for the
> > > current target ('-x') may be present (KBUILD_CFLAGS is used for these
> > > tests instead of KBUILD_AFLAGS). Inside try-run, the macro behind
> > > as-instr and as-option, I see
> > >
> > >   clang-17: error: unsupported option '-mno-prefixed' for target 'powerpc64le-linux-gnu'
> > >   clang-17: error: unsupported option '-mno-pcrel' for target 'powerpc64le-linux-gnu'
> > >   clang-17: error: unsupported option '-mno-altivec' for target 'powerpc64le-linux-gnu'
> > >   clang-17: error: unsupported option '-mno-vsx' for target 'powerpc64le-linux-gnu'
> > >   clang-17: error: unsupported option '-mno-mma' for target 'powerpc64le-linux-gnu'
> > >   clang-17: error: unsupported option '-mno-spe' for target 'powerpc64le-linux-gnu'
> > >
> > > This has come up recently elsewhere in PowerPC, see
> > > commit 2b694fc96fe3 ("powerpc/boot: Disable power10 features after
> > > BOOTAFLAGS assignment"). While I think it is dubious that clang errors
> > > on these flags for the assembler target, this is already fixed on the
> > > Linux side by using KBUILD_AFLAGS for these make macros.
> > >
> > > I am preparing a series of d5c8d6e0fa61 and its dependencies for 6.1 but
> > > I want to do sufficient build testing first, which is currently running
> > > for me. Would you be able to point your matrix to [2] to make sure
> > > everything works properly with both GCC and LLVM? It is a work in
> > > progress as the second patch in the stack needs a proper commit message
> > > but it is the diff I expect to ship so that it all that matters.
> >
> > We'll start building [2] with GCC and LLVM by using tuxplans and
> > get back to you.
> 
> LKFT has been configured to run GCC and LLVM in total 205 builds
> and all the builds have passed on your tree / branch [2]. You can find
> the list of builds including kselftest, perf, rcutorture, kunit, kmemleak
> and many more combinations and architectures.
> 
> I request you to review the list of builds results and test results on
> projects page [3] [4]. I do not find any regressions compared with
> mainline master as sanity testing.

Thanks a lot for testing!

> Do you think LKFT should build your tree / branch often ?
> We are happy to test anytime.

No, this is an exceptional circumstance, not the norm. If I need wider
testing done in the future, I will keep you all in mind :)

> Thanks Daniel and Anders for your work.
> 
> build_names: that got tested and all have passed.
> 

<snip>

Great! I sent along the 6.1 backports now:

https://lore.kernel.org/20230612-6-1-asssembler-target-llvm-17-v1-0-75605d553401@kernel.org/

Thanks again for testing and the report, cheers!
Nathan

clang nightly builds failing on PowerPc

[Dan Carpenter]

Hi the Clang nightly builds are failing on PowerPC with the
ppc64e_defconfig.  They started failing on Sept 11.  Clang is failing on
PowerPC in both linux-next and stable so it seems like something changed
in Clang and not the kernel.

Unfortunately I don't have ready access to the /tmp/vgetrandom-fef220.c
file that was generated, but hopefully these logs are enough to reproduce
the issue.

regards,
dan carpenter

tuxmake --target-arch=powerpc --kconfig=ppc64e_defconfig --toolchain=clang-nightly --wrapper=none --environment=KBUILD_BUILD_TIMESTAMP=@1758237451 --environment=KBUILD_BUILD_USER=tuxmake --environment=KBUILD_BUILD_HOST=tuxmake --environment=KCFLAGS=-ffile-prefix-map=/home/tuxbuild/.cache/tuxmake/builds/1/build/= --runtime=podman --image=855116176053.dkr.ecr.us-east-1.amazonaws.com/tuxmake/powerpc_clang-nightly LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld config default kernel xipkernel modules dtbs dtbs-legacy debugkernel headers
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 LD=powerpc64le-linux-gnu-ld 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 LD=powerpc64le-linux-gnu-ld
fatal error: error in backend: Cannot select: 0x60f13bcf8910: ch,glue = PPCISD::CALL_NOP 0x60f13bcf5e70, TargetGlobalAddress:i32<ptr @__arch_chacha20_blocks_nostack> 0, Register:i64 $x3, Register:i64 $x4, Register:i64 $x5, Register:i64 $x6, Register:i64 $x2, RegisterMask:Untyped, 0x60f13bcf5e70:1
  0x60f13bcf5e70: ch,glue = CopyToReg 0x60f13bcf8750, Register:i64 $x6, 0x60f13bcf5cb0, 0x60f13bcf8750:1
    0x60f13bcf5cb0: i64 = zero_extend 0x60f13bcf8600
      0x60f13bcf8600: i32 = srl 0x60f13bcf8280, Constant:i32<6>
        0x60f13bcf8280: i32,ch = CopyFromReg 0x60f13bc01ec0, Register:i32 %43
    0x60f13bcf8750: ch,glue = CopyToReg 0x60f13bcf6490, Register:i64 $x5, 0x60f13bcf8440, 0x60f13bcf6490:1
      0x60f13bcf8440: i64 = zero_extend FrameIndex:i32<0>
      0x60f13bcf6490: ch,glue = CopyToReg 0x60f13bcf8590, Register:i64 $x4, 0x60f13bcf69d0, 0x60f13bcf8590:1
        0x60f13bcf69d0: i64 = zero_extend 0x60f13bcf5bd0
          0x60f13bcf5bd0: i32,ch = CopyFromReg 0x60f13bc01ec0, Register:i32 %3
        0x60f13bcf8590: ch,glue = CopyToReg 0x60f13bcf6960, Register:i64 $x3, 0x60f13bcf68f0
          0x60f13bcf68f0: i64 = zero_extend 0x60f13bcf8520
            0x60f13bcf8520: i32,ch = CopyFromReg 0x60f13bc01ec0, Register:i32 %44
In function: __c_kernel_getrandom
clang: error: clang frontend command failed with exit code 70 (use -v to see invocation)
Debian clang version 22.0.0 (++20250917082822+6c8fcd6089b9-1~exp1~20250917203011.86)
Target: powerpc-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm-22/bin
clang: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /tmp/vgetrandom-fef220.c
clang: note: diagnostic msg: /tmp/vgetrandom-fef220.sh
clang: note: diagnostic msg: 

********************
fatal error: error in backend: Don't know how to emit this value.
make[3]: *** [/builds/linux/arch/powerpc/kernel/vdso/Makefile:91: arch/powerpc/kernel/vdso/vgetrandom-32.o] Error 1
clang: error: clang frontend command failed with exit code 70 (use -v to see invocation)
Debian clang version 22.0.0 (++20250917082822+6c8fcd6089b9-1~exp1~20250917203011.86)
Target: powerpc-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm-22/bin
clang: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /tmp/vgettimeofday-43498a.c
clang: note: diagnostic msg: /tmp/vgettimeofday-43498a.sh
clang: note: diagnostic msg: 

********************
make[3]: *** [/builds/linux/arch/powerpc/kernel/vdso/Makefile:89: arch/powerpc/kernel/vdso/vgettimeofday-32.o] Error 1
make[3]: Target 'include/generated/vdso32-offsets.h' not remade because of errors.
make[2]: *** [/builds/linux/arch/powerpc/Makefile:388: vdso_prepare] Error 2
make[2]: Target '__all' not remade because of errors.
make[1]: *** [/builds/linux/Makefile:248: __sub-make] Error 2
make[1]: Target '__all' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target '__all' not remade because of errors.
rm -rf /home/tuxbuild/.cache/tuxmake/builds/1/build/modinstall
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build INSTALL_MOD_STRIP=1 INSTALL_MOD_PATH=/home/tuxbuild/.cache/tuxmake/builds/1/build/modinstall ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld modules_install
make[3]: *** No rule to make target 'modules.order', needed by '/home/tuxbuild/.cache/tuxmake/builds/1/build/modinstall/lib/modules/6.17.0-rc6/modules.order'.
make[3]: *** No rule to make target 'modules.builtin', needed by '/home/tuxbuild/.cache/tuxmake/builds/1/build/modinstall/lib/modules/6.17.0-rc6/modules.builtin'.
make[3]: *** No rule to make target 'modules.builtin.modinfo', needed by '/home/tuxbuild/.cache/tuxmake/builds/1/build/modinstall/lib/modules/6.17.0-rc6/modules.builtin.modinfo'.
make[3]: Target '__modinst' not remade because of errors.
make[2]: *** [/builds/linux/Makefile:1917: modules_install] Error 2
make[1]: *** [/builds/linux/Makefile:248: __sub-make] Error 2
make[1]: Target 'modules_install' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target 'modules_install' not remade because of errors.
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build INSTALL_DTBS_PATH=/home/tuxbuild/.cache/tuxmake/builds/1/build/dtbsinstall/dtbs ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld dtbs
rm -rf /home/tuxbuild/.cache/tuxmake/builds/1/build/dtbsinstall
mkdir -p /home/tuxbuild/.cache/tuxmake/builds/1/build/dtbsinstall/dtbs
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build INSTALL_DTBS_PATH=/home/tuxbuild/.cache/tuxmake/builds/1/build/dtbsinstall/dtbs ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld dtbs_install
tar --sort=name --owner=tuxmake:1000 --group=tuxmake:1000 --mtime=@1758237451 --clamp-mtime -caf /home/tuxbuild/.cache/tuxmake/builds/1/build/dtbs.tar.xz -C /home/tuxbuild/.cache/tuxmake/builds/1/build/dtbsinstall dtbs
rm -rf /home/tuxbuild/.cache/tuxmake/builds/1/build/install_hdr
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build INSTALL_HDR_PATH=/home/tuxbuild/.cache/tuxmake/builds/1/build/install_hdr/ ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld headers_install
tar --sort=name --owner=tuxmake:1000 --group=tuxmake:1000 --mtime=@1758237451 --clamp-mtime -caf /home/tuxbuild/.cache/tuxmake/builds/1/build/headers.tar.xz -C /home/tuxbuild/.cache/tuxmake/builds/1/build/install_hdr .

Re: clang nightly builds failing on PowerPc

[Nathan Chancellor]

Hi Dan,

On Fri, Sep 19, 2025 at 02:17:41PM +0300, Dan Carpenter wrote:
> Hi the Clang nightly builds are failing on PowerPC with the
> ppc64e_defconfig.  They started failing on Sept 11.  Clang is failing on
> PowerPC in both linux-next and stable so it seems like something changed
> in Clang and not the kernel.
> 
> Unfortunately I don't have ready access to the /tmp/vgetrandom-fef220.c
> file that was generated, but hopefully these logs are enough to reproduce
> the issue.

Indeed, thanks a lot for the report. I was able to reproduce this
locally, bisect LLVM to find the problematic commit, and report it
upstream:

https://github.com/llvm/llvm-project/pull/157206#issuecomment-3313700961

Hopefully it can be resolved quickly.

Cheers,
Nathan