From owner-freebsd-current  Tue Nov 30  4:17:15 1999
Delivered-To: freebsd-current@freebsd.org
Received: from not.demophon.com (vpn.iscape.fi [195.170.146.67])
	by hub.freebsd.org (Postfix) with ESMTP id 16C6715878
	for <current@freebsd.org>; Tue, 30 Nov 1999 04:17:12 -0800 (PST)
	(envelope-from will@not.demophon.com)
Received: (from will@localhost)
	by not.demophon.com (8.9.3/8.8.7) id OAA52918;
	Tue, 30 Nov 1999 14:15:18 +0200 (EET)
	(envelope-from will)
To: current@freebsd.org
Subject: Re: kernel: -mpreferred-stack-boundary=2 ??
References: <Pine.BSF.4.10.9911300236160.7938-100000@current1.whistle.com.newsgate.clinet.fi>, <86d7ssi61u.fsf@not.demophon.com> <3843B63D.6A81ABD7@scc.nl.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 30 Nov 1999 14:15:17 +0200
In-Reply-To: Marcel Moolenaar's message of "30 Nov 1999 13:57:12 +0200"
Message-ID: <86bt8ci3ai.fsf@not.demophon.com>
Lines: 10
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> 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.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message