From: John David Anglin <dave.anglin@bell.net>
To: glaubitz@physik.fu-berlin.de, 45214@debbugs.gnu.org
Cc: Helge Deller <deller@gmx.de>,
Michael Karcher <debian@mkarcher.dialup.fu-berlin.de>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#45214: guile segfaults on 32-bit big-endian targets
Date: Sat, 12 Dec 2020 18:22:26 -0500 [thread overview]
Message-ID: <95a4dfbc-9b3f-d875-3e23-6e7ca23a0ab2@bell.net> (raw)
In-Reply-To: <e8c2c373-344e-a105-35d2-5b59e0961693@physik.fu-berlin.de>
On 2020-12-12 5:47 p.m., John Paul Adrian Glaubitz wrote:
> And m68k and powerpc most likely.
This could also be a bug on 32-bit targets:
CC libguile_3.0_la-hash.lo
../../guile/libguile/hash.c: In function 'narrow_string_hash':
../../guile/libguile/hash.c:118:34: warning: left shift count >= width of type [
-Wshift-count-overflow]
118 | ret = (((unsigned long) c) << 32) | b;
\
| ^~
../../guile/libguile/hash.c:128:3: note: in expansion of macro 'JENKINS_LOOKUP3_
HASHWORD2'
128 | JENKINS_LOOKUP3_HASHWORD2 (str, len, ret);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../../guile/libguile/hash.c: In function 'wide_string_hash':
../../guile/libguile/hash.c:118:34: warning: left shift count >= width of type [-Wshift-count-overflow]
118 | ret = (((unsigned long) c) << 32) | b; \
| ^~
Regards,
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2020-12-12 23:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 21:26 bug#45214: guile segfaults on 32-bit big-endian targets John Paul Adrian Glaubitz
2020-12-12 22:00 ` John David Anglin
2020-12-12 22:02 ` John Paul Adrian Glaubitz
2021-02-25 15:24 ` Efraim Flashner
2021-04-14 14:18 ` Efraim Flashner
2021-04-14 19:19 ` John Paul Adrian Glaubitz
2021-04-15 11:50 ` Efraim Flashner
2021-04-15 13:23 ` John Paul Adrian Glaubitz
2021-10-03 9:38 ` John Paul Adrian Glaubitz
2021-10-04 16:08 ` John David Anglin
2021-10-04 16:11 ` John Paul Adrian Glaubitz
2020-12-12 22:21 ` John David Anglin
2020-12-12 22:30 ` John David Anglin
2020-12-12 22:44 ` John David Anglin
2020-12-12 22:47 ` John Paul Adrian Glaubitz
2020-12-12 23:22 ` John David Anglin [this message]
2020-12-13 18:06 ` John David Anglin
2020-12-13 18:08 ` John Paul Adrian Glaubitz
2021-02-08 23:24 ` John David Anglin
2021-02-09 13:03 ` John David Anglin
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95a4dfbc-9b3f-d875-3e23-6e7ca23a0ab2@bell.net \
--to=dave.anglin@bell.net \
--cc=45214@debbugs.gnu.org \
--cc=debian@mkarcher.dialup.fu-berlin.de \
--cc=deller@gmx.de \
--cc=glaubitz@physik.fu-berlin.de \
--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.
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).