From owner-freebsd-hackers@FreeBSD.ORG  Fri Oct 31 05:10:16 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id ABB477C9
 for <freebsd-hackers@freebsd.org>; Fri, 31 Oct 2014 05:10:16 +0000 (UTC)
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com
 [209.85.220.53])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 7F4EF626
 for <freebsd-hackers@freebsd.org>; Fri, 31 Oct 2014 05:10:16 +0000 (UTC)
Received: by mail-pa0-f53.google.com with SMTP id kx10so6969384pab.12
 for <freebsd-hackers@freebsd.org>; Thu, 30 Oct 2014 22:10:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:content-type:mime-version:subject:from
 :in-reply-to:date:cc:content-transfer-encoding:message-id:references
 :to; bh=R5znHJRsCXwfTND2wigREdLP6cKbMb1BKhbDeTnfLpw=;
 b=cJdz76FEbCeFcW+mUDbPkKzPH8ONEkMXf3rhqEaa350nSqBAl5E1hyMDUxzbjKSRv/
 zK9tAzd7nquddCcffzjqrCbRZj0Ssw2Vbv/wQUC9iOyqL67GP9jOEsS0dpPtN9Y8ABVD
 xsxPZk+UgJwGhowbZzTetA9iP1IKRKCmUH8cPExFxfqrQSUoDncAFkKzjhTr8vYrILZU
 ARP69R882dvqRApHeWxpmwMhltiyNRJHXclHq57Ih/1N/Z9+4bijIZxyr8VBa0rkfY0Z
 g+4yqSlZEtfflORwgyAYqhduzRkZsmPaJZm9x2e26SBHKb1i8Ex0syl3gsjk6DFqll0v
 aIbQ==
X-Gm-Message-State: ALoCoQlyG6FQwdk5YeOVT+xvT2hFgc9P1RsoiGodCxb3crcBI/DgLufHIuT35q8XLIqMxsYktLBA
X-Received: by 10.66.145.234 with SMTP id sx10mr10488134pab.130.1414732209148; 
 Thu, 30 Oct 2014 22:10:09 -0700 (PDT)
Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net.
 [24.6.220.224])
 by mx.google.com with ESMTPSA id s9sm8689609pdp.1.2014.10.30.22.10.06
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Thu, 30 Oct 2014 22:10:07 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: how to kernel printf a int64_t?
From: Tim Kientzle <tim@kientzle.com>
In-Reply-To: <439339249.2551223.1414702876172.JavaMail.root@uoguelph.ca>
Date: Thu, 30 Oct 2014 22:09:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <97A82163-E78D-457E-B649-B243B41A6C6F@kientzle.com>
References: <439339249.2551223.1414702876172.JavaMail.root@uoguelph.ca>
To: Rick Macklem <rmacklem@uoguelph.ca>
X-Mailer: Apple Mail (2.1878.6)
Cc: Freebsd hackers list <freebsd-hackers@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 05:10:16 -0000


On Oct 30, 2014, at 2:01 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote:

> Hi,
>=20
> I feel kinda dumb asking this, but...
>       int64_t i;
>=20
>       printf("%qd\n", (u_quad_t)i);
>=20
> works but looks dorky, to put it technically;-).
> Is there a better way to printf() a int64_t in the kernel?

I often use the following to print large integers:

    printf(=93%jd\n=94, (intmax_t)i);

Tim