Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Thomas Koenig <tkoenig@netcologne.de>
Newsgroups: comp.arch
Subject: Re: Cost of handling misaligned access
Date: Thu, 13 Feb 2025 19:21:36 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <volgo0$31n5t$1@dont-email.me>
References: <5lNnP.1313925$2xE6.991023@fx18.iad>
 <vnosj6$t5o0$1@dont-email.me> <2025Feb3.075550@mips.complang.tuwien.ac.at>
 <volg1m$31ca1$1@dont-email.me>
Injection-Date: Thu, 13 Feb 2025 20:21:36 +0100 (CET)
Injection-Info: dont-email.me; posting-host="de60826e7578cdb0fbe89d1d0430cc4c";
	logging-data="3202237"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+tKJIXhoLQFloJ5JS9JFGzoMNhCSI5Jo8="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:sBgj9yhQdy4k9H0nQ5iyYgF7xDc=
Bytes: 1412

On 2025-02-13, Marcus <m.delete@this.bitsnbites.eu> wrote:

> The problem arises when the programmer *deliberately* does unaligned
> loads and stores in order to improve performance. Or rather, if the
> programmer knows that the hardware supports unaligned loads and stores,
> he/she can use that to write faster code in some special cases.

Or the compiler or standard library author can do the same.