From owner-freebsd-current@freebsd.org  Tue Nov 17 08:09:18 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87C2EA31A95
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 17 Nov 2015 08:09:18 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 19F1411EE
 for <freebsd-current@freebsd.org>; Tue, 17 Nov 2015 08:09:17 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kostik@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tAH896CK030442
 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Tue, 17 Nov 2015 10:09:06 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tAH896CK030442
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id tAH896FN030433;
 Tue, 17 Nov 2015 10:09:06 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Tue, 17 Nov 2015 10:09:06 +0200
From: Konstantin Belousov <kostikbel@gmail.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Cc: Warner Losh <imp@bsdimp.com>, Justin Hibbits <chmeeedalf@gmail.com>,
 FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: CFT: uintmax_t rman
Message-ID: <20151117080906.GA58629@kib.kiev.ua>
References: <75C2B97F-3C5E-49E3-A584-DE84463889FC@gmail.com>
 <0F3B8FF2-E54E-446F-8D4E-415A1111EF4D@bsdimp.com>
 <alpine.GSO.1.10.1511161923000.26829@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.GSO.1.10.1511161923000.26829@multics.mit.edu>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 08:09:18 -0000

On Mon, Nov 16, 2015 at 07:25:54PM -0500, Benjamin Kaduk wrote:
> Channeling my inner bde (maybe?), the typedef is probably helpful, but
> uintmax_t seems less so.  uintmax_t has no guaranteed ABI, so a
> fixed-width type like uint64_t seems beter, assuming that uintmax_t is
> currently uint64_t everywhere (which I think is the case but did not
> verify).

The statement about {u}intmax_t not having a guaranteed ABI is wrong,
I believe.  You cannot change the type after it is exposed.

I am sure that ANSI C or POSIX would introduce intthistimerealmax_t after
long long long type is added (only half-joking).