From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: me@enzu.ru, 46111@debbugs.gnu.org
Subject: bug#46111: Reverting fns.c hash function due to OpenBSD/SPARC64 compile breaking
Date: Thu, 28 Jan 2021 11:14:47 -0500 [thread overview]
Message-ID: <jwvbld9vy2m.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zh0t59q4.fsf@igel.home> (Andreas Schwab's message of "Thu, 28 Jan 2021 17:04:19 +0100")
Andreas Schwab [2021-01-28 17:04:19] wrote:
> On Jan 28 2021, Stefan Monnier wrote:
>
>>>> - I'd guess that the bus error is due to alignment restrictions.
>>>> What hardware is this running on?
>>> See the Subject: it's SPARC64.
>>
>> I mean the actual hardware, not the architecture.
>
> Strict alignment is a property of the architecture, not the hardware.
IIRC some RISC architectures *allowed* errors on unaligned memory
accesses without requiring it, making it a property of the hardware.
Stefan
next prev parent reply other threads:[~2021-01-28 16:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 6:37 bug#46111: Reverting fns.c hash function due to OpenBSD/SPARC64 compile breaking Ahmed Khanzada
2021-01-26 6:57 ` Ahmed Khanzada
2021-01-26 11:15 ` Eli Zaretskii
2021-01-28 4:06 ` Ahmed Khanzada
2021-01-28 13:58 ` Eli Zaretskii
2021-01-28 15:09 ` Stefan Monnier
2021-01-28 15:19 ` Eli Zaretskii
2021-01-28 15:44 ` Stefan Monnier
2021-01-28 15:52 ` Stefan Monnier
2021-01-28 16:17 ` Stefan Monnier
2021-01-28 16:22 ` Andreas Schwab
2021-01-28 17:22 ` Eli Zaretskii
2021-01-28 17:30 ` Stefan Monnier
2021-01-28 16:04 ` Andreas Schwab
2021-01-28 16:14 ` Stefan Monnier [this message]
2021-01-26 9:36 ` Philipp Stephani
2021-01-26 11:12 ` Eli Zaretskii
2021-01-26 11:17 ` Andreas Schwab
2021-01-26 11:43 ` Eli Zaretskii
2021-01-26 11:49 ` Andreas Schwab
2021-01-26 15:36 ` Eli Zaretskii
2021-01-27 7:42 ` Richard Stallman
2021-01-27 8:24 ` Andreas Schwab
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbld9vy2m.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=46111@debbugs.gnu.org \
--cc=me@enzu.ru \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).