Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <526F1D46.30604@nicta.com.au>
Date: Tue, 29 Oct 2013 13:28:22 +1100
From: Matthew Fernandez <matthew.fernandez@...ta.com.au>
To: <musl@...ts.openwall.com>
Subject: printf format macros

Hi all,

This may be a silly question, but why does there seem to be no 64-bit
compatibility in the printf macros in inttypes.h? The relevant section is:

25 #if UINTPTR_MAX == UINT64_MAX
26 #define __PRI64  "l"
27 #else
28 #define __PRI64  "ll"
29 #endif

as compared to Glibc's:

49 # if __WORDSIZE == 64
50 #  define __PRI64_PREFIX    "l"
51 #  define __PRIPTR_PREFIX   "l"
52 # else
53 #  define __PRI64_PREFIX    "ll"
54 #  define __PRIPTR_PREFIX
55 # endif

We use Musl C on 32- and 64-bit platforms and I'm looking for a way to
write printf format strings word-length-independently in an application.
I'm not currently subscribed to the list so please CC me personally when
replying.

Thanks in advance,
Matthew

________________________________

The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.