From owner-freebsd-sparc64@FreeBSD.ORG Sun Feb 22 22:13:01 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 421AE16A4CE for ; Sun, 22 Feb 2004 22:13:01 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E85D43D1D for ; Sun, 22 Feb 2004 22:13:01 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 3AFF25309; Mon, 23 Feb 2004 07:12:59 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 54EC45308; Mon, 23 Feb 2004 07:12:52 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 37EDA33C6F; Mon, 23 Feb 2004 07:12:52 +0100 (CET) To: Garance A Drosihn References: <20040215060047.GA62840@dhcp01.pn.xcllnt.net> <20040215165913.M30161@grogged.dyndns.org> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Mon, 23 Feb 2004 07:12:52 +0100 In-Reply-To: (Garance A. Drosihn's message of "Sun, 22 Feb 2004 23:16:58 -0500") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: sparc64@freebsd.org Subject: Re: Problem with DHCLIENT vs 64-bit time_t X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 06:13:01 -0000 Garance A Drosihn writes: > When comparing the warnings from i386 to those from sparc64, > sparc64 sees about 50 extra warnings about: > warning: cast increases required alignment of target type > > Would this be a possible cause of inconsistent (and usually broken) > behavior in a program? Do we need to try to fix all of those? Probably. I'm not sure it's worth it. The code looks like whoever wrote it knew zip about C. You should try to get a newer version imported and hope the ISC fixed it themselves. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no