Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 8 Jan 2002 12:11:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 8 Jan 2002 12:11:37 -0500 Received: from mxzilla4.xs4all.nl ([194.109.6.48]:54544 "EHLO mxzilla4.xs4all.nl") by vger.kernel.org with ESMTP id ; Tue, 8 Jan 2002 12:11:27 -0500 Date: Tue, 8 Jan 2002 18:11:21 +0100 From: jtv To: Anthony DeRobertis Cc: Jacques Gelinas , linux-kernel@vger.kernel.org Subject: Re: Whizzy New Feature: Paged segmented memory Message-ID: <20020108181121.A12696@xs4all.nl> In-Reply-To: <20020107224525.8a899969dbcd@remtk.solucorp.qc.ca> <20020108122225.B11855@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from asd@suespammers.org on Tue, Jan 08, 2002 at 02:05:09PM +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 08, 2002 at 02:05:09PM +0000, Anthony DeRobertis wrote: > > Change gcc. Recompile world. All should work, assuming your gcc changes are > bug-free, no one made assumptions about stack layout, no one wrote assembly > code, etc. [In other words, after 4 months of debugging you might get X > running again...] And, of course, the same for all other software. But for a highly secure project, for instance, that might be worth it. > Some architectures have hardware assistance for downward growing stacks. One > example is 68K. I think x86 does too. OTOH, I don't think PPC does, though I > haven't read the Green Book recently. 68K has predecrement/postincrement addressing modes (I'm not sure that counts as "forcing" the stack to grow downwards); PPC has a symmetrical load/store-with-update IIRC. Jeroen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/