From owner-freebsd-alpha Fri Sep 4 15:15:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15405 for freebsd-alpha-outgoing; Fri, 4 Sep 1998 15:15:40 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15394 for ; Fri, 4 Sep 1998 15:15:35 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id IAA12990; Sat, 5 Sep 1998 08:27:42 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199809042227.IAA12990@cimlogic.com.au> Subject: Re: Help - No htonq, ntohq In-Reply-To: from Simon Shapiro at "Sep 4, 98 06:10:25 pm" To: shimon@simon-shapiro.org Date: Sat, 5 Sep 1998 08:27:40 +1000 (EST) Cc: freebsd-alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon Shapiro wrote: > Can anyone suggest a clean, portable way to support binary competability on > 64bit integers between an Alpha and IA? int64_t & u_int64_t > We have hton{l,s} but these are good only for 16 & 32 bit values. I think hton{l,s} should be kept strictly for _network_ code. > What is the exact Alpha byte order? 12345678, 87654321, 43218765, ... ^^^^^^^^ Little endian. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message