From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 15:04:42 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 D441716A41C for ; Fri, 10 Jun 2005 15:04:42 +0000 (GMT) (envelope-from gerarra@tin.it) Received: from vsmtp2.tin.it (vsmtp2.tin.it [212.216.176.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CE3C43D49 for ; Fri, 10 Jun 2005 15:04:39 +0000 (GMT) (envelope-from gerarra@tin.it) Received: from ims3a.cp.tin.it (192.168.70.103) by vsmtp2.tin.it (7.0.027) id 42A8BA670005734F; Fri, 10 Jun 2005 17:04:38 +0200 Received: from [192.168.70.227] by ims3a.cp.tin.it with HTTP; Fri, 10 Jun 2005 17:04:37 +0200 Date: Fri, 10 Jun 2005 17:04:37 +0200 Message-ID: <429C8E8F00012B5F@ims3a.cp.tin.it> In-Reply-To: <00aa01c56dc4$e93fb050$92a7cb52@rekon> From: gerarra@tin.it To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable X-Originating-IP: 213.140.22.70 Cc: reko.turja@liukuma.net Subject: RE: X86 machine code enter and FreeBSD kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 15:04:43 -0000 >I received no reply on this question at questions mailing list, so I try= > >asking this here. Hope I'm not asking this in completely wrong list. > >In recent discussion in OpenWatcom lists it was noticed that at least >certain addressing modes of assembler ENTER instruction causes a crash >when used in Linux. GCC circumnavigates this by not emitting ENTER >instructions in machine code. Linus's comment on the above issue can be >found on: > >http://groups.google.co.nz/groups?selm=3D7i86ni%24b7n%241%40palladium.tr= ansmeta.com > >What's the status of the above "feature" in FreeBSD, does the kernel >support the >whole x86 instruction set without similar cut corners? > >-Reko Mainly, I think gcc sets stack by hands beacause ENTER does a lot of dirt= y work. If you see x86 pseudocode, it perform a lot of wasting work... howe= ver, what you proposed is not a bug, just a way of ruling stack frames. rookie