From: Heiko Carstens <hca@linux.ibm.com>
To: Juergen Christ <jchrist@linux.ibm.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 8/8] s390/tishift: Convert __ashlti3(), __ashrti3(), __lshrti3() to C
Date: Mon, 8 Jun 2026 10:55:56 +0200 [thread overview]
Message-ID: <20260608085556.34400Bae-hca@linux.ibm.com> (raw)
In-Reply-To: <507926e4-d6a5-45f6-822c-1196e6d5d18a-jchrist@linux.ibm.com>
On Mon, Jun 08, 2026 at 10:19:39AM +0200, Juergen Christ wrote:
> > There is no reason to have __ashlti3(), __ashrti3(), and __lshrti3()
> > implemented in C. Convert them all to C, which allows the compiler to
> > optimize the code if newer instructions allow that.
>
> I guess there is a typo and you meant to write "implemented in
> Assembler"?
Yes, of course.
next prev parent reply other threads:[~2026-06-08 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 5:37 [PATCH v2 0/8] Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 1/8] s390/purgatory: Enforce z10 minimum architecture level Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 2/8] s390: Add .noinstr.text to boot and purgatory linker scripts Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 3/8] s390/string: Convert memmove() to C Heiko Carstens
2026-06-08 8:01 ` Juergen Christ
2026-06-08 9:14 ` Heiko Carstens
2026-06-08 9:20 ` Juergen Christ
2026-06-08 5:37 ` [PATCH v2 4/8] s390/string: Convert memset() " Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 5/8] s390/string: Convert memcpy() " Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 6/8] s390/string: Convert memset(16|32|64)() " Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 7/8] s390/memmove: Optimize backward copy case Heiko Carstens
2026-06-08 5:37 ` [PATCH v2 8/8] s390/tishift: Convert __ashlti3(), __ashrti3(), __lshrti3() to C Heiko Carstens
2026-06-08 8:19 ` Juergen Christ
2026-06-08 8:55 ` Heiko Carstens [this message]
2026-06-08 9:24 ` [PATCH v2 0/8] Juergen Christ
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=20260608085556.34400Bae-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=jchrist@linux.ibm.com \
--cc=linux-s390@vger.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