From owner-freebsd-arm@FreeBSD.ORG Thu Jan 24 18:03:24 2008 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 537D916A46C for ; Thu, 24 Jan 2008 18:03:24 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 0B4E113C461 for ; Thu, 24 Jan 2008 18:03:23 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id ADFC41736D; Thu, 24 Jan 2008 19:03:22 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAXxw-BiLk-4; Thu, 24 Jan 2008 19:03:17 +0100 (CET) Received: from [212.61.27.67] (opteron.digiware.nl [212.61.27.67]) by mail.digiware.nl (Postfix) with ESMTP id 52F3417331; Thu, 24 Jan 2008 19:03:17 +0100 (CET) Message-ID: <4798D2E2.4000809@digiware.nl> Date: Thu, 24 Jan 2008 19:03:14 +0100 From: Willem Jan Withagen Organization: Digiware User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <20080118.145436.-1540399028.imp@bsdimp.com> <20080124114039.GF79134@zibbi.meraka.csir.co.za> <479880A7.1030107@digiware.nl> <20080124.084828.1608359032.imp@bsdimp.com> <864pd386mj.fsf@ds4.des.no> In-Reply-To: <864pd386mj.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-arm@freebsd.org Subject: Re: sshd broken on arm? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2008 18:03:24 -0000 Dag-Erling Smørgrav wrote: > "M. Warner Losh" writes: >> Actually, the above fix *IS* the correct fix for arm given the ABI >> that we're using... > > No. The correct fix is one that will be acceptable to the upstream > vendor, who has a different perspective on things than we do. Well that was more what I would expect and both answers are hard. Because it requires either: - the openSSH people to add something that is awkward to say the least. - get the compiler guys to do "the right thing", so now you have to convince them that they need to do a better analysis. --WjW