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 17:21:00 -0500 [thread overview]
Message-ID: <155f44c6-dda1-dec9-cc4c-b029a73e65d7@bell.net> (raw)
In-Reply-To: <56553e87-ec27-d287-9e5b-fc501bc4b2dc@physik.fu-berlin.de>
On 2020-12-12 4:26 p.m., John Paul Adrian Glaubitz wrote:
> I assume the crash has got something to do how values are packed and unpacked
> into the SCM object type. I have not been able to find the problem yet myself,
> unfortunately which is why I am reporting this issue here.
I see this in scm.h:
/* The 0?: constructions makes sure that the code is never executed, and
that there is no performance hit. However, the alternative is
compiled, and does generate a warning when used with the wrong
pointer type. We use a volatile pointer type to avoid warnings from
clang.
The Tru64 and ia64-hp-hpux11.23 compilers fail on `case (0?0=0:x)'
statements, so for them type-checking is disabled. */
# if defined __DECC || defined __HP_cc
# define SCM_UNPACK(x) ((scm_t_bits) (x))
# else
# define SCM_UNPACK(x) ((scm_t_bits) (0? (*(volatile SCM *)0=(x)): x))
# endif
Regards,
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2020-12-12 22:21 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 [this message]
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
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=155f44c6-dda1-dec9-cc4c-b029a73e65d7@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).