From: Hanlin Song <pgeorge8929@gmail.com>
To: guoren@kernel.org
Cc: Hanlin Song <pgeorge8929@gmail.com>,
linux-csky@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] csky: Fix ABIv2 memcmp() s1 alignment check
Date: Mon, 6 Jul 2026 18:39:32 +0800 [thread overview]
Message-ID: <20260706103932.20961-1-pgeorge8929@gmail.com> (raw)
In-Reply-To: <20260623112438.33022-1-pgeorge8929@gmail.com>
Hi Guo Ren and C-SKY maintainers,
Gentle ping on this patch.
My understanding is that r3 holds the original s1 pointer after r0 is
cleared, so the alignment check should use r3 instead of r0. I also
tested this on a CK860f chip, and the patched version was faster in my
unaligned memcmp test.
I may be missing some C-SKY ABIv2 detail, so any feedback would be
appreciated.
Thanks,
Hanlin
next prev parent reply other threads:[~2026-07-06 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 11:24 [PATCH] csky: Fix ABIv2 memcmp() s1 alignment check Hanlin Song
2026-07-06 10:39 ` Hanlin Song [this message]
2026-07-07 3:15 ` Guo Ren
2026-07-07 3:47 ` Hanlin Song
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=20260706103932.20961-1-pgeorge8929@gmail.com \
--to=pgeorge8929@gmail.com \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.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: 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