From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
 [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 493611B309
 for <dev@dpdk.org>; Tue, 13 Feb 2018 21:59:16 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id E580720AE6;
 Tue, 13 Feb 2018 15:59:15 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
 by compute1.internal (MEProxy); Tue, 13 Feb 2018 15:59:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 content-transfer-encoding:content-type:date:from:message-id
 :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=
 mesmtp; bh=mowkcu2gpjsQdDjlvJhD5at1dIKr4o2xhWlEWt/uDS0=; b=ixf5U
 sPt1U2l+alW6LdoUnO8cYofg3DgRre24paBCfJg36AoE7wRl64rHdYksw7bCUYFr
 y3hou5uAHWjcOkOJqxrRCv0m7MVKlaLLXs4JLZeHG99W4+MAWSZ9qVWWbioX6MjX
 SUmV4R2Z780CfnPDFONIUD+QNMzEgBxe0NoqPU=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=content-transfer-encoding:content-type
 :date:from:message-id:mime-version:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=fm2; bh=mowkcu2gpjsQdDjlvJhD5at1dIKr4
 o2xhWlEWt/uDS0=; b=bpxvJ4VLtWZC7fW+F4abO4vWsIXo97e7iBAwYWE8lSBio
 7eTtBVQ92lHeFuHnyHXJ7ABOtC0e3tsmPPY8VynBc8mV39rMPZKUzvsIHMNJh4iC
 8JIdoDyRVa2PuBlKQi1QIRDLuiBMAY4/u3H43/kb3To7rwnnVfm3nr6M/kl4HHMi
 h0a9YVDE13lfiGAyL2hyKt33BDfHMBs4MorhU/hU2Zw74StWF1q2QGCp+pgn/yE7
 zoYQZcUHyrMVqM6XeNZpqZIrN5HebOEM6Q5J2UXyucbMoWe8tY40CzI2GcGjSsVM
 MdDWo1I131v8nT6w85hyCp1a+R5+y4sCgwHEY+N1A==
X-ME-Sender: <xms:o1GDWlkVuuwbujPsJp2dB4lrWcXwPNACkWxxH7C0O2kuZSdiMCcAeA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 95146246D5
 for <dev@dpdk.org>; Tue, 13 Feb 2018 15:59:15 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Date: Tue, 13 Feb 2018 21:59:05 +0100
Message-ID: <1626400.QN1GMNLe81@xps>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: [dpdk-dev] 32-bit compilation & debug logs
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Feb 2018 20:59:16 -0000

Hi all,

There is a very common pattern with build failures in DPDK.
When compiling in 32-bit mode, there are some mismatches between
printf format "%lu" / "%lx" and the size of the data being 64-bit.
In 32-bit mode, a long is 32 bits long :)
That's why "%lx" must be replaced by "%" PRIx64.

	long     -> %lx
	uint64_t -> %PRIx64

Most of the times, using %l is wrong (except when printing a long).
So next time you write %l, please think "I am probably wrong".

For the existing codebase, please grep "%l".
There are probably some remaining wrong "%l" which are not detected
when compiling, because the code is in debug functions never enabled.
Note that debug code should be tested but there can be some forgotten
code paths.

Thanks