From: jtv <jtv@xs4all.nl>
To: Anthony DeRobertis <asd@suespammers.org>
Cc: Jacques Gelinas <jack@solucorp.qc.ca>, linux-kernel@vger.kernel.org
Subject: Re: Whizzy New Feature: Paged segmented memory
Date: Tue, 8 Jan 2002 18:11:21 +0100 [thread overview]
Message-ID: <20020108181121.A12696@xs4all.nl> (raw)
In-Reply-To: <20020107224525.8a899969dbcd@remtk.solucorp.qc.ca> <BD98BECA-0407-11D6-804A-00039355CFA6@suespammers.org> <20020108122225.B11855@xs4all.nl> <E16NwsH-0005Ud-00@asd.ppp0.com>
In-Reply-To: <E16NwsH-0005Ud-00@asd.ppp0.com>; from asd@suespammers.org on Tue, Jan 08, 2002 at 02:05:09PM +0000
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
next prev parent reply other threads:[~2002-01-08 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 3:45 Whizzy New Feature: Paged segmented memory Jacques Gelinas
2002-01-08 7:17 ` Anthony DeRobertis
2002-01-08 11:22 ` jtv
2002-01-08 14:05 ` Anthony DeRobertis
2002-01-08 14:14 ` Richard B. Johnson
2002-01-08 19:33 ` Anthony DeRobertis
2002-01-08 19:45 ` Richard B. Johnson
2002-01-08 17:11 ` jtv [this message]
2002-01-08 19:32 ` Anthony DeRobertis
-- strict thread matches above, loose matches on Subject: below --
2002-01-08 13:42 Jacques Gelinas
2002-01-06 14:14 Marcin Tustin
2002-01-06 18:32 ` Gábor Lénárt
2002-01-06 20:41 ` Kevin Krieser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020108181121.A12696@xs4all.nl \
--to=jtv@xs4all.nl \
--cc=asd@suespammers.org \
--cc=jack@solucorp.qc.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.