From owner-freebsd-hackers@FreeBSD.ORG Wed May 5 10:54:11 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48AE316A4CE; Wed, 5 May 2004 10:54:11 -0700 (PDT) Received: from gabby.gsicomp.on.ca (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [69.193.82.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF0F443D31; Wed, 5 May 2004 10:54:07 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by gabby.gsicomp.on.ca (8.12.9p2/8.12.9) with ESMTP id i45IEDVH002264; Wed, 5 May 2004 14:16:03 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <00d401c432c9$430394e0$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Deng XueFeng" , "John Baldwin" References: <20040502132115.C583.DSNOFE@hotmail.com><200405031322.37241.jhb@FreeBSD.org> <20040504090033.B046.DSNOFE@hotmail.com> Date: Wed, 5 May 2004 13:46:17 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: hackers Subject: Re: Is this LOST?? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2004 17:54:11 -0000 > > On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote: > > > I found the htonl implemention in libc for i386 is not sync with the > > > kern. > > > > > > sys use bswap for swaping the int. but libc still use xchg. > > > IS THIS LOST? > > > > It's because libc still supports 80386 which doesn't have bswap (introduced on > > the 486 IIRC). The kernel only supports 486+ unless you explicitly build an > > 80386 kernel, which won't use bswap for htonl(). > > Since 5-current kernel do not support 80386. > why keep libc(5-current) support 80386? The 5-current kernel *does* support 80386 -- you have to recompile your kernel to add 80386 support first. -- Matt Emmerton