From: Florian Weimer <fweimer@redhat.com>
To: musl@lists.openwall.com
Subject: [musl] __WORDSIZE on x32
Date: Tue, 23 Nov 2021 20:51:36 +0100 [thread overview]
Message-ID: <875ysips53.fsf@oldenburg.str.redhat.com> (raw)
This looks a bid suspicious:
arch/x32/bits/reg.h:#undef __WORDSIZE
arch/x32/bits/reg.h:#define __WORDSIZE 32
arch/x32/bits/user.h:#undef __WORDSIZE
arch/x32/bits/user.h:#define __WORDSIZE 64
I don't know if it causes any actual problems. I discovered it while
checking whether musl defines/uses __WORDSIZE.
Thanks,
Florian
next reply other threads:[~2021-11-23 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 19:51 Florian Weimer [this message]
2021-11-23 20:14 ` Rich Felker
2021-11-23 20:22 ` Florian Weimer
2022-03-08 21:59 ` Rich Felker
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ysips53.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=musl@lists.openwall.com \
/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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).