Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 8 Feb 2013 17:14:08 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: printf warning with uintmax_t

On Fri, Feb 08, 2013 at 11:10:39PM +0100, Jens Gustedt wrote:
> Hi again,
> with musl-gcc the following test program produces a bogus warning
> concerning uintmax_t on my machine (ubuntu amd64)
> 
> Jens
> 
> #include <stdio.h>
> #include <stdint.h>
> 
> void toto(void) {
>   uintmax_t val = 42;
>   printf("%jX\n", val);
> }

It looks like we're not matching the ABI convention gcc expects, where
[u]intmax_t is the lowest-rank type capable of storing the full
integer range (i.e. long on 64-bit systems).

This should probably be fixed, if for no other reason than C++ ABI
issues.

Any objections?

Rich

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.