From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2758 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: printf warning with uintmax_t Date: Fri, 8 Feb 2013 17:14:08 -0500 Message-ID: <20130208221408.GN20323@brightrain.aerifal.cx> References: <1360361439.23424.95.camel@eris.loria.fr> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1360361660 3196 80.91.229.3 (8 Feb 2013 22:14:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Feb 2013 22:14:20 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2759-gllmg-musl=m.gmane.org@lists.openwall.com Fri Feb 08 23:14:41 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1U3wDP-0003jX-JU for gllmg-musl@plane.gmane.org; Fri, 08 Feb 2013 23:14:39 +0100 Original-Received: (qmail 32467 invoked by uid 550); 8 Feb 2013 22:14:20 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 32459 invoked from network); 8 Feb 2013 22:14:20 -0000 Content-Disposition: inline In-Reply-To: <1360361439.23424.95.camel@eris.loria.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:2758 Archived-At: 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 > #include > > 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