From: Ard Biesheuvel <ardb@kernel.org> To: Borislav Petkov <bp@alien8.de> Cc: Nick Desaulniers <ndesaulniers@google.com>, kernel test robot <lkp@intel.com>, Geert Uytterhoeven <geert+renesas@glider.be>, kbuild-all@lists.01.org, clang-built-linux <clang-built-linux@googlegroups.com>, LKML <linux-kernel@vger.kernel.org>, "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@kernel.org> Subject: Re: [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' Date: Wed, 23 Dec 2020 23:43:45 +0100 [thread overview] Message-ID: <CAMj1kXG58+DdfA9RDE9gnELf8ZT0dTX+g8D+3W0pVM8RUSF_OQ@mail.gmail.com> (raw) In-Reply-To: <20201223210405.GB28724@zn.tnic> Hello Boris, On Wed, 23 Dec 2020 at 22:04, Borislav Petkov <bp@alien8.de> wrote: > > 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@alien8.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 > I hope this report is not holding up the PR for efi/core? > ... > > > 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! > > :-) > Likewise!
WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ardb@kernel.org> To: kbuild-all@lists.01.org Subject: Re: [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' Date: Wed, 23 Dec 2020 23:43:45 +0100 [thread overview] Message-ID: <CAMj1kXG58+DdfA9RDE9gnELf8ZT0dTX+g8D+3W0pVM8RUSF_OQ@mail.gmail.com> (raw) In-Reply-To: <20201223210405.GB28724@zn.tnic> [-- Attachment #1: Type: text/plain, Size: 2629 bytes --] Hello Boris, On Wed, 23 Dec 2020 at 22:04, Borislav Petkov <bp@alien8.de> wrote: > > 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@alien8.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 > I hope this report is not holding up the PR for efi/core? > ... > > > 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! > > :-) > Likewise!
next prev parent reply other threads:[~2020-12-23 22:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-18 1:03 [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' kernel test robot 2020-12-18 1:03 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' kernel test robot 2020-12-23 18:36 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' Borislav Petkov 2020-12-23 18:36 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' Borislav Petkov 2020-12-23 20:02 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' Nick Desaulniers 2020-12-23 20:02 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' Nick Desaulniers 2020-12-23 21:04 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' Borislav Petkov 2020-12-23 21:04 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' Borislav Petkov 2020-12-23 22:43 ` Ard Biesheuvel [this message] 2020-12-23 22:43 ` Ard Biesheuvel 2020-12-24 8:55 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' Borislav Petkov 2020-12-24 8:55 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' Borislav Petkov 2020-12-24 9:10 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2,a2' Ard Biesheuvel 2020-12-24 9:10 ` [tip:efi/core 3/7] /tmp/slab-258052.s:9870: Error: unrecognized opcode `zext.b a2, a2' Ard Biesheuvel
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=CAMj1kXG58+DdfA9RDE9gnELf8ZT0dTX+g8D+3W0pVM8RUSF_OQ@mail.gmail.com \ --to=ardb@kernel.org \ --cc=bp@alien8.de \ --cc=clang-built-linux@googlegroups.com \ --cc=geert+renesas@glider.be \ --cc=kbuild-all@lists.01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ --cc=ndesaulniers@google.com \ --cc=x86@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: linkBe 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.