From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46111@debbugs.gnu.org, me@enzu.ru
Subject: bug#46111: Reverting fns.c hash function due to OpenBSD/SPARC64 compile breaking
Date: Thu, 28 Jan 2021 10:44:09 -0500 [thread overview]
Message-ID: <jwvmtwtw035.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8335ylytpf.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jan 2021 17:19:56 +0200")
>> - 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.
[ I know most RISC processors started with a restriction that they only
allowed aligned memory accesses, but AFAIK they've changed stance
since (IIUC the extra hardware can be very little, sometimes even less
than the hardware that would be needed to implement the ad-hoc
"support instructions" used to do the unaligned access as a sequence
of instructions).
It's one of the RISC simplifications that just didn't pan out. ]
>> - AFAICT from the backtrace, `ptr` points to a plain normal ELisp
>> string's content, yet these are supposed to be aligned, so what's
>> going on here
> I wondered that myself.
And what did you conclude? ;-)
Stef
next prev parent reply other threads:[~2021-01-28 15:44 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 [this message]
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
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=jwvmtwtw035.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=46111@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=me@enzu.ru \
/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).