Date: Fri, 10 Jun 2005 17:04:37 +0200 From: gerarra@tin.it To: freebsd-hackers@freebsd.org Cc: reko.turja@liukuma.net Subject: RE: X86 machine code enter and FreeBSD kernel Message-ID: <429C8E8F00012B5F@ims3a.cp.tin.it> In-Reply-To: <00aa01c56dc4$e93fb050$92a7cb52@rekon>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?429C8E8F00012B5F>