From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 5a and optimization
Date: Thu, 19 Jan 2006 10:49:56 -0500 [thread overview]
Message-ID: <acb178fec4c3be89cd56a9b7ef1ff45f@plan9.bell-labs.com> (raw)
In-Reply-To: <88B50F0E-168B-40DE-B795-1CFEBF74C272@gmail.com>
One way is to make it TEXT, e.g. the multiboot header and GDT stuff
in /sys/src/9/pc/l.s.
Agreed, the loaders don't make such things easy to do, but writing
assembler and making odd format binaries is the exception, not the
rule.
--jim
On Thu Jan 19 06:31:30 EST 2006, noah.evans@gmail.com wrote:
> How do you keep the linker from optimizing away your rom headers and
> other data? I had to put a noop in front of my first text section to
> keep the linker from putting the main loop in front of it. I also had
> to code the branch past the rom header in hex to keep the linker from
> eating the header(it's unreachable).
>
> Best,
>
> Noah
next prev parent reply other threads:[~2006-01-19 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 11:30 Noah Evans
2006-01-19 15:49 ` jmk [this message]
2006-01-19 15:59 ` Noah Evans
2006-01-19 17:05 ` Bruce Ellis
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=acb178fec4c3be89cd56a9b7ef1ff45f@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).