From owner-freebsd-alpha  Sat Sep  5 11:03:54 1998
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA25057
          for freebsd-alpha-outgoing; Sat, 5 Sep 1998 11:03:54 -0700 (PDT)
          (envelope-from owner-freebsd-alpha@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA25050
          for <freebsd-alpha@FreeBSD.ORG>; Sat, 5 Sep 1998 11:03:50 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 1314 invoked by uid 1000); 5 Sep 1998 19:05:57 -0000
Message-ID: <XFMail.980905150557.shimon@simon-shapiro.org>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19980905171747.45786@follo.net>
Date: Sat, 05 Sep 1998 15:05:57 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-T<Ako6fc!xyO!<qETO3]"NFbiV!}=/kj5G1L>H61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'<b{Ioa^9\-Z$3!Z7-
 ;\X0`\'JZI~c>\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro <shimon@simon-shapiro.org>
To: Eivind Eklund <eivind@yes.no>
Subject: Re: Help - No htonq, ntohq
Cc: freebsd-alpha@FreeBSD.ORG, John Birrell <jb@cimlogic.com.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Eivind Eklund, On 05-Sep-98 you wrote:
>  On Sat, Sep 05, 1998 at 08:27:40AM +1000, John Birrell wrote:
> > 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.
>  
>  I think Simon is working on sharing binary data between Intel and
>  Alpha (running with shared disk).  Saying 'strictly for network code'
>  doesn't help solve the problem at all.  May I suggest the introduction
>  of
>  
>  hton16s(l,s)    ntoh16s(l,s)
>  hton16u(l,s) ntoh16u(l,s)
>  hton32s(l,s) ntoh32s(l,s)
>  hton32u(l,s) ntoh32u(l,s)
>  hton64s(l,s) ntoh64s(l,s)
>  hton64u(l,s) ntoh64u(l,s)
>  
>  as a much more clear way of handling the naming?  (I placed the
>  sign-indicator after the number of bits, to avoid confusion with
>  htons()).  This also give a clear answer to the question 'what should
>  I use for 64-bit' :-)
>  
>  Eivind.

Thanx!  Am I to understand that what I want does not exist?  I saw a
reference to something in /usr/include/nfs/xdr_subs.h but am not clear what
value it has.  I'd rather have some concensus first.

Simon


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message