public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Evan Green <evan@rivosinc.com>
Cc: libc-alpha@sourceware.org,  vineetg@rivosinc.com,
	 slewis@rivosinc.com, Florian Weimer <fweimer@redhat.com>,
	 palmer@rivosinc.com
Subject: Re: [PATCH v13 7/7] riscv: Add and use alignment-ignorant memcpy
Date: Sat, 02 Mar 2024 11:33:03 +0100	[thread overview]
Message-ID: <87v864c49s.fsf@linux-m68k.org> (raw)
In-Reply-To: <20240227225644.724901-8-evan@rivosinc.com> (Evan Green's message of "Tue, 27 Feb 2024 14:56:43 -0800")

On Feb 27 2024, Evan Green wrote:

> For CPU implementations that can perform unaligned accesses with little
> or no performance penalty, create a memcpy implementation that does not
> bother aligning buffers. It will use a block of integer registers, a
> single integer register, and fall back to bytewise copy for the
> remainder.

How has that been tested?  It causes memory corruption.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2024-03-02 10:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 22:56 [PATCH v13 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green
2024-02-27 22:56 ` [PATCH v13 1/7] riscv: Add Linux hwprobe syscall support Evan Green
2024-02-27 22:56 ` [PATCH v13 2/7] linux: Introduce INTERNAL_VSYSCALL Evan Green
2024-02-27 22:56 ` [PATCH v13 3/7] riscv: Add hwprobe vdso call support Evan Green
2024-02-27 22:56 ` [PATCH v13 4/7] riscv: Add __riscv_hwprobe pointer to ifunc calls Evan Green
2024-02-27 22:56 ` [PATCH v13 5/7] riscv: Enable multi-arg ifunc resolvers Evan Green
2024-02-27 22:56 ` [PATCH v13 6/7] riscv: Add ifunc helper method to hwprobe.h Evan Green
2024-02-27 22:56 ` [PATCH v13 7/7] riscv: Add and use alignment-ignorant memcpy Evan Green
2024-03-02 10:33   ` Andreas Schwab [this message]
2024-03-04 18:30     ` Adhemerval Zanella Netto
2024-03-04 19:35       ` Evan Green
2024-03-02 13:52   ` Andreas Schwab
2024-03-01 15:19 ` [PATCH v13 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Palmer Dabbelt

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=87v864c49s.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=evan@rivosinc.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@rivosinc.com \
    --cc=slewis@rivosinc.com \
    --cc=vineetg@rivosinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).