linux-kernel - Re: [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 23 Dec 2020 22:04:05 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     kernel test robot <lkp@...el.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        kbuild-all@...ts.01.org,
        clang-built-linux <clang-built-linux@...glegroups.com>,
        LKML <linux-kernel@...r.kernel.org>,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
        Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized
 opcode `zext.b a2,a2'

On Wed, Dec 23, 2020 at 12:02:33PM -0800, Nick Desaulniers wrote:
> On Wed, Dec 23, 2020 at 10:36 AM Borislav Petkov <bp@...en8.de> wrote:
> >
> > On Fri, Dec 18, 2020 at 09:03:14AM +0800, kernel test robot wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi/core
> > > head:   b283477d394ac41ca59ee20eb9293ae9002eb1d7
> > > commit: 6edcf9dc2e1aff3aa1f5a69ee420fb30dd0e968a [3/7] efi/libstub: EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER should not default to yes
> > > config: riscv-randconfig-r022-20201217 (attached as .config)
> > > compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project cee1e7d14f4628d6174b33640d502bff3b54ae45)
> > > reproduce (this is a W=1 build):
> > >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > >         chmod +x ~/bin/make.cross
> > >         # install riscv cross compiling tool for clang build
> > >         # apt-get install binutils-riscv64-linux-gnu
> > >         # https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=6edcf9dc2e1aff3aa1f5a69ee420fb30dd0e968a
> > >         git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > >         git fetch --no-tags tip efi/core
> > >         git checkout 6edcf9dc2e1aff3aa1f5a69ee420fb30dd0e968a
> > >         # save the attached .config to linux build tree
> > >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv

...

> Thanks for taking the time to try to repro, and the report.  Just
> curious, which clang are you using?  Is it from your distro?  If you
> have `llc` installed, can you send me the output of `llc --version`?
> 
> The reason I ask is; unlike GCC, Clang ships with all non-experimental
> backends on by default, and relies on `--target=<triple>` when cross
> compiling.

I just did the steps outlined above, in the mail. Look for "reproduce
(this is a W=1 build):" above. I guess that make.cross script needs to
be fixed to do the --target thing, I haven't looked.

clang is downloaded by the script, just do the steps and you'll see:

> > cd: received redirection to `https://download.01.org/0day-ci/cross-package/'
> > lftpget -c https://download.01.org/0day-ci/cross-package/./clang-latest/clang.tar.xz

Thx.

> Happy holidays+new year.

Ditto!

:-)

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette