Date: Sun, 5 Jun 2005 16:25:13 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Matt Emmerton <matt@gsicomp.on.ca> Cc: freebsd-current@freebsd.org, Martin <nakal@nurfuerspam.de> Subject: Re: Optimizing libc/string for amd64(?) Message-ID: <20050605062513.GB31558@cirb503493.alcatel.com.au> In-Reply-To: <000701c5696f$0dee3b10$1200a8c0@gsicomp.on.ca> References: <42A242D1.4000002@nurfuerspam.de> <000701c5696f$0dee3b10$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2005-Jun-04 21:36:53 -0400, Matt Emmerton wrote: >It would probably be better to use int64_t and int32_t instead of long/int, >in order to make the intention more obvious. The intent is to use the widest, efficiently supported type. This is 'long' on all of our architectures. int64_t has to be simulated on i386 and is therefore not an idea choice. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050605062513.GB31558>