1996-12-20 - Re: Code+Data separation

Header Data

From: Bill Frantz <frantz@netcom.com>
To: cypherpunks@toad.com
Message Hash: 27d338d1c9c60c5ffc56a1aa860d941545a1a487abfa6342f9134dae243e9ef8
Message ID: <v03007804aedfd804957e@[204.31.236.106]>
Reply To: <v02140b01aedf4fba9ec3@[192.0.2.1]>
UTC Datetime: 1996-12-20 05:48:36 UTC
Raw Date: Thu, 19 Dec 1996 21:48:36 -0800 (PST)

Raw message

From: Bill Frantz <frantz@netcom.com>
Date: Thu, 19 Dec 1996 21:48:36 -0800 (PST)
To: cypherpunks@toad.com
Subject: Re: Code+Data separation
In-Reply-To: <v02140b01aedf4fba9ec3@[192.0.2.1]>
Message-ID: <v03007804aedfd804957e@[204.31.236.106]>
MIME-Version: 1.0
Content-Type: text/plain


At 12:08 PM -0800 12/19/96, Peter Hendrickson wrote:
>Are there any modern processors which keep the code and data separated?

Many modern processors keep separate L1 caches for code and data.  Sparc
architecture requires a special instruction to say, "I have just used data
operations to change this part of the program."  I assume that program
fetchers and linkers must use this instruction.

Keeping separate main memory makes program loading and in-memory dynamic
linking hard.  The linker's data is the processor's program.


-------------------------------------------------------------------------
Bill Frantz       | I still read when I should | Periwinkle -- Consulting
(408)356-8506     | be doing something else.   | 16345 Englewood Ave.
frantz@netcom.com | It's a vice. - R. Heinlein | Los Gatos, CA 95032, USA







Thread