linux-kernel - Re: How to printk/sprintf uint64_t on Sparc without format and argument types mismatch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100616192934.GX20317@bombadil.infradead.org>
Date:	Wed, 16 Jun 2010 15:29:34 -0400
From:	Kyle McMartin <kyle@...artin.ca>
To:	Vladislav Bolkhovitin <vst@...b.net>
Cc:	sparclinux@...r.kernel.org, Simone Ricci <simone.ricci@...il.com>,
	scst-devel@...ts.sourceforge.net, Joe Eykholt <jeykholt@...co.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: How to printk/sprintf uint64_t on Sparc without format and
	argument types mismatch

On Wed, Jun 16, 2010 at 11:08:03PM +0400, Vladislav Bolkhovitin wrote:
> scst/src/scst_targ.c:2136: warning: format ?%llx? expects type ?long  
> long unsigned int?, but argument 4 has type ?uint64_t?.
>
> It is because on Sparc uint64_t defined as unsigned long, but on x86 -  
> as unsigned long long.
>

>From your other mail, it looks like you're using 2.6.26... this is
ancient! Sparc has since been fixed to use unsigned long long for u64.

commit 9018113649348c689da107166c05d436cd52e7bf
Author: Sam Ravnborg <sam@...nborg.org>
Date:   Tue Jan 6 13:19:28 2009 -0800

    sparc64: Use unsigned long long for u64.

regards, Kyle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/