From: David Wuertele <dave+gmane@wuertele.com>
To: musl@lists.openwall.com
Subject: Re: Am I using PRIxPTR wrong? Musl-libc complains, glibc doesn't
Date: Tue, 14 Jan 2014 21:34:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20140114T223406-69@post.gmane.org> (raw)
In-Reply-To: <20140114210601.GF1685@port70.net>
Szabolcs Nagy <nsz <at> port70.net> writes:
> * David Wuertele <dave+gmane <at> wuertele.com> [2014-01-14 20:36:36 +0000]:
> > ** Both native (x86_64 glibc) and target (arm musl-libc) define
> > ** PRIxPTR as "lx", but uintptr_t as unsigned int:
>
> musl defines it to "x" on 32bit archs
>
> please check
>
> arm-linux-musleabishf-gcc -E -dD inttypes.h
>
> in particular UINTPTR_MAX should be set to UINT32_MAX
> and __PRIPTR to ""
>
>
Here's what it says. I don't see __PRIPTR in there.
$ PATH=PATH:../bin arm-linux-musleabishf-gcc -E -dD inttypes.h | grep UINTPTR_MAX
#define __UINTPTR_MAX__ 4294967295U
#define UINTPTR_MAX UINT32_MAX
$ PATH=PATH:../bin arm-linux-musleabishf-gcc -E -dD inttypes.h | grep __PRIPTR
$ PATH=PATH:../bin arm-linux-musleabishf-gcc -E -dD inttypes.h | grep __PRI
#define __PRI64 "ll"
#define PRId64 __PRI64 "d"
#define PRIdLEAST64 __PRI64 "d"
#define PRIdFAST64 __PRI64 "d"
#define PRIi64 __PRI64 "i"
#define PRIiLEAST64 __PRI64 "i"
#define PRIiFAST64 __PRI64 "i"
#define PRIo64 __PRI64 "o"
#define PRIoLEAST64 __PRI64 "o"
#define PRIoFAST64 __PRI64 "o"
#define PRIu64 __PRI64 "u"
#define PRIuLEAST64 __PRI64 "u"
#define PRIuFAST64 __PRI64 "u"
#define PRIx64 __PRI64 "x"
#define PRIxLEAST64 __PRI64 "x"
#define PRIxFAST64 __PRI64 "x"
#define PRIX64 __PRI64 "X"
#define PRIXLEAST64 __PRI64 "X"
#define PRIXFAST64 __PRI64 "X"
#define PRIdMAX __PRI64 "d"
#define PRIiMAX __PRI64 "i"
#define PRIoMAX __PRI64 "o"
#define PRIuMAX __PRI64 "u"
#define PRIxMAX __PRI64 "x"
#define PRIXMAX __PRI64 "X"
#define SCNd64 __PRI64 "d"
#define SCNdLEAST64 __PRI64 "d"
#define SCNdFAST64 __PRI64 "d"
#define SCNi64 __PRI64 "i"
#define SCNiLEAST64 __PRI64 "i"
#define SCNiFAST64 __PRI64 "i"
#define SCNu64 __PRI64 "u"
#define SCNuLEAST64 __PRI64 "u"
#define SCNuFAST64 __PRI64 "u"
#define SCNo64 __PRI64 "o"
#define SCNoLEAST64 __PRI64 "o"
#define SCNoFAST64 __PRI64 "o"
#define SCNx64 __PRI64 "x"
#define SCNxLEAST64 __PRI64 "x"
#define SCNxFAST64 __PRI64 "x"
#define SCNdMAX __PRI64 "d"
#define SCNiMAX __PRI64 "i"
#define SCNoMAX __PRI64 "o"
#define SCNuMAX __PRI64 "u"
#define SCNxMAX __PRI64 "x"
$
prev parent reply other threads:[~2014-01-14 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 20:36 David Wuertele
2014-01-14 20:59 ` Rich Felker
2014-01-14 21:06 ` Szabolcs Nagy
2014-01-14 21:20 ` Rich Felker
2014-01-14 21:37 ` David Wuertele
2014-01-14 21:45 ` Rich Felker
2014-01-14 21:34 ` David Wuertele [this message]
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=loom.20140114T223406-69@post.gmane.org \
--to=dave+gmane@wuertele.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).