From: Noah Evans <noah.evans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 5a and optimization
Date: Fri, 20 Jan 2006 00:59:59 +0900 [thread overview]
Message-ID: <386F3D23-0B29-4781-B9AC-87DB921101B7@gmail.com> (raw)
In-Reply-To: <acb178fec4c3be89cd56a9b7ef1ff45f@plan9.bell-labs.com>
Yeah, I put it in l.s(probably should put it in rom.s but who knows).
The linker eats the text if I leave the branch in. So I put the
branch in a WORD and(thanks to Charles' advice) use -E to go to the
initial TEXT _rom section.
Very true about the rom weirdness.
Thank you very much for the advice. I really appreciate the support.
Noah
On Jan 20, 2006, at 12:49 AM, jmk@plan9.bell-labs.com wrote:
> 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:59 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
2006-01-19 15:59 ` Noah Evans [this message]
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=386F3D23-0B29-4781-B9AC-87DB921101B7@gmail.com \
--to=noah.evans@gmail.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).