From owner-freebsd-current Tue Nov 30 5:27: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id EC95D158A4 for ; Tue, 30 Nov 1999 05:26:55 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA54474 for current@FreeBSD.org; Tue, 30 Nov 1999 14:12:08 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 30 Nov 1999 14:12:03 +0100 From: Marcel Moolenaar Message-ID: <3843CD23.6221988A@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <86bt8ci3ai.fsf@not.demophon.com> Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: > > > What about commercial and/or third party KLDs? They fail to work if they > > don't also set -preferred-stack-boundry=2, right? > > Oops, I accidentally replied to this privately. > > Anyhow, I'll repeat it here - stack alignment does *not* break > link-compatibility. It does not change calling conventions, it just > adds padding after the args to ensure that local variables can be > predictably aligned. So, how does aligning stackframes affect the inherently static property of code size then? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message