All of
 help / color / mirror / Atom feed
From: Vasily Gorbik <>
To: Nathan Chancellor <>
Cc: Heiko Carstens <>,
	Alexander Gordeev <>,,,
Subject: Re: s390 defconfig fails to build after 4afeb670710efa5cd5ed8b1d9f2d22d6ce332bcc
Date: Mon, 28 Mar 2022 23:44:26 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <YkH/rRikE2CilpqU@dev-arch.thelio-3990X>

On Mon, Mar 28, 2022 at 11:34:21AM -0700, Nathan Chancellor wrote:
> Hi all,
> Apologies if this has been reported or fixed already, I did not see a
> report when searching and it is reproducible as of
> commit 7dcfe50f58d2 ("s390/pci: rename get_zdev_by_bus() to
> zdev_from_bus()") in s390/linux.git.
> Our continuous integration noticed a build failure on next-20220328 in
> arch/s390/kernel/entry.S, which does not appear to be compiler specific,
> as I can reproduce this with GCC easily:
> $ make -skj"$(nproc)" ARCH=s390 CROSS_COMPILE=s390x-linux-gnu- defconfig arch/s390/kernel/entry.o
> arch/s390/kernel/entry.S: Assembler messages:
> arch/s390/kernel/entry.S:335: Error: Unrecognized opcode: `jgnop'
> arch/s390/kernel/entry.S:493: Error: Unrecognized opcode: `jgnop'
> arch/s390/kernel/entry.S:494: Error: Unrecognized opcode: `jgnop'

Thank you for reporting this!

jgnop mnemonic has been introduced with binutils commit
b10b530a4566 ("IBM Z: Add support for HLASM extended mnemonics")

and is part of binutils-2_36 and newer.

I fixed it by using old "brcl 0,0" alternative here:

  reply	other threads:[~2022-03-28 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 18:34 s390 defconfig fails to build after 4afeb670710efa5cd5ed8b1d9f2d22d6ce332bcc Nathan Chancellor
2022-03-28 21:44 ` Vasily Gorbik [this message]
2022-03-28 21:52   ` Nathan Chancellor

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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 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.