From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Data segment vs BSS
Date: Tue, 31 Jan 2006 12:06:56 +0000 [thread overview]
Message-ID: <63b4280d39d09df613ecc84900deaf7b@terzarima.net> (raw)
In-Reply-To: <6a1747e8e1b545a6b23612bdb1f8d776@vitanuova.com>
> more important, the compiler had to ensure that no data was marked for program
> memory until it had checked that it was never accessed indirectly (because
> then the called function would use the wrong instruction). again, const
sorry, i meant `indirectly by something that might access both forms of data'.
for instance, it allowed a table's address to be taken by
p = &table (or plain p = table for an array)
and tracked that nothing was assigned through p, and that p
was not assigned elsewhere to point to writable data.
next prev parent reply other threads:[~2006-01-31 12:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 4:36 Noah Evans
2006-01-31 5:09 ` jmk
2006-01-31 5:35 ` Noah Evans
2006-01-31 5:48 ` jmk
2006-01-31 5:54 ` Ronald G Minnich
2006-01-31 8:48 ` Noah Evans
2006-01-31 15:03 ` Ronald G Minnich
2006-01-31 15:12 ` Noah Evans
2006-01-31 16:05 ` Ronald G Minnich
2006-01-31 16:11 ` Noah Evans
2006-01-31 16:24 ` Russ Cox
2006-01-31 16:30 ` Paul Lalonde
2006-01-31 16:52 ` C H Forsyth
2006-01-31 17:33 ` Ronald G Minnich
2006-01-31 11:44 ` C H Forsyth
2006-01-31 12:06 ` Charles Forsyth [this message]
2006-01-31 12:39 ` Charles Forsyth
2006-01-31 13:06 ` Noah Evans
2006-01-31 13:44 ` Charles Forsyth
2006-01-31 12:39 ` Charles Forsyth
2006-01-31 15:05 ` Ronald G Minnich
2006-01-31 9:03 ` Noah Evans
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=63b4280d39d09df613ecc84900deaf7b@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).