From: Heiko Carstens <hca@linux.ibm.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sven Schnelle <svens@linux.ibm.com>, linux-s390@vger.kernel.org
Subject: Re: Build error around 'aghik' after commit 1256e70a082a ("s390/ftrace: enable HAVE_FUNCTION_GRAPH_RETVAL")
Date: Wed, 26 Jul 2023 07:42:25 +0200 [thread overview]
Message-ID: <20230726054225.6242-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20230725211105.GA224840@dev-arch.thelio-3990X>
Hi Nathan,
> Apologies if this has been reported/fixed already, I checked the s390
> tree but I did not see any changes there nor did I find anything when
> searching lore. After commit 1256e70a082a ("s390/ftrace: enable
> HAVE_FUNCTION_GRAPH_RETVAL") in -next, I see the following errors when
> building Debian's configuration [1], which selects CONFIG_MARCH_Z10=y.
>
> GCC/binutils:
>
> arch/s390/kernel/mcount.S: Assembler messages:
> arch/s390/kernel/mcount.S:140: Error: Unrecognized opcode: `aghik'
>
> clang:
>
> arch/s390/kernel/mcount.S:140:2: error: instruction requires: distinct-ops
> aghik %r3,%r15,160
> ^
>
> It seems like there is already some handling for this situation in
> mcount.S but my knowledge of s390 assembly is basically non-existent,
> hence this report in lieu of a patch. I am more than happy to provide
> any additional information or test any patches if necessary.
Thanks, for reporting. Yet another bug where an instruction which is only
available on later machines (in this case z196) is used unconditionally. I
really need to add some automated test so this kind of trivial bugs don't
escape.
Will fix.
prev parent reply other threads:[~2023-07-26 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 21:11 Build error around 'aghik' after commit 1256e70a082a ("s390/ftrace: enable HAVE_FUNCTION_GRAPH_RETVAL") Nathan Chancellor
2023-07-26 5:42 ` Heiko Carstens [this message]
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=20230726054225.6242-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=svens@linux.ibm.com \
/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