From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3271 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: sign (in)consistency between architectures Date: Wed, 1 May 2013 20:00:15 +0200 Message-ID: <20130501180015.GN12689@port70.net> References: <51814B3F.4040005@eservices.virginia.edu> 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 1367431232 21361 80.91.229.3 (1 May 2013 18:00:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 May 2013 18:00:32 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3275-gllmg-musl=m.gmane.org@lists.openwall.com Wed May 01 20:00:32 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 1UXbKN-0001aY-UA for gllmg-musl@plane.gmane.org; Wed, 01 May 2013 20:00:28 +0200 Original-Received: (qmail 13915 invoked by uid 550); 1 May 2013 18:00:27 -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 13907 invoked from network); 1 May 2013 18:00:27 -0000 Content-Disposition: inline In-Reply-To: <51814B3F.4040005@eservices.virginia.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3271 Archived-At: * Z. Gilboa [2013-05-01 13:05:03 -0400]: > The current architecture-specific type definitions > (arch/*/bits/alltypes.h) seem to entail the following inconsistent > signed/unsigned types: > > type x86_64 i386 > ------------------------------- > uid_t unsigned signed > gid_t unsigned signed > dev_t unsigned signed > clock_t signed unsigned i can verify that glibc uses unsigned uid_t,gid_t,dev_t and signed clock_t of course applications should not depend on the signedness, but if they appear in a c++ api then the difference can cause problems and cock_t may be used in arithmetics where signedness matters