From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Data segment vs BSS
Date: Tue, 31 Jan 2006 00:09:03 -0500 [thread overview]
Message-ID: <98cca1d3171d88afdc40c9a1c4ff0e62@plan9.bell-labs.com> (raw)
In-Reply-To: <F831EAF1-40CC-4DE3-B542-911D688E19A7@gmail.com>
The normal Plan 9 binary format assumes the BSS starts immediately
after the data, there is no place in the header to specify otherwise.
So, you want to use a different header format, e.g. ELF or one of
the machine-specific boot formats, see /sys/src/cmd/?l/asm.c for
examples. There may be one there already that suits, or you can easily
add another for your particular environment.
But how do you separate out the constant data?
On Mon Jan 30 23:36:55 EST 2006, noah.evans@gmail.com wrote:
> Hey, quick 2l question. Is there any way to keep constant values in
> ROM? If possible I'd like to keep the data section entirely in ROM
> and only keep the BSS section in RAM. However, both sections seem to
> be inextricably linked.
>
> What's the proper way to deal with this?
>
> Noah
next prev parent reply other threads:[~2006-01-31 5:09 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 [this message]
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
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=98cca1d3171d88afdc40c9a1c4ff0e62@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--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).