From: Pieter Arnout <pieter@powerescape.com>
To: binutils@sources.redhat.com
Subject: HELP with linker script!!!
Date: Thu, 31 Mar 2005 14:42:00 -0000 [thread overview]
Message-ID: <13ab0c503312082c7af572c83f523f4f@powerescape.com> (raw)
I read the the Red Hat manual "Using ld, the GNU Linker", but I'm
having trouble. Essentially, I'd like to take specific symbols and
assign them to a memory region, rather than just take a section and
assign it to a memory region. I can obtain the symbol values and symbol
type from the objdump or nm output. The only examples offered in the
manual, however, only define the output sections .bss and .data by just
assigning everything from the .bss and .data input sections to it:
SECTIONS
{
. = 0x10000;
.text : { *(.text) }
. = 0x8000000;
.data : { *(.data) }
.bss : { *(.bss) }
}
I want some finer control. Does anyone know how I can go about
ultimately assigning specific symbols (or data structures if you will)
to a memory region? Should / can I create a section (much like .text,
.data or .bss above) in the linker script and call it "my_section" and
assign a list of symbols to "my_section"? Is this how I would go about
accomplishing what I want? If so do I reference the symbols by name or
by value when I call them out in the SECTIONS command? How does that
look like?
Additionally, where do I define the start and end regions of my stack
and heap? I use .bss for uninitialized variables, .data for initialized
variables, but how do I reference the beginning and end of stack and
the beginning and end of heap?
I need answers urgently.
Thanks so much for your help!
Pieter
next reply other threads:[~2005-03-31 0:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 14:42 Pieter Arnout [this message]
2005-03-31 15:50 ` Nick Clifton
[not found] ` <29c1ff0410ff9cc2b88a3ad82d1938aa@powerescape.com>
2005-04-01 11:27 ` Nick Clifton
2005-04-01 12:53 ` Vincent Rubiolo
2005-04-01 14:05 ` Nick Clifton
2005-04-01 14:13 ` Dave Korn
2005-04-01 14:34 ` Andreas Schwab
2005-04-01 16:53 ` Pieter Arnout
2005-04-04 9:39 ` Vincent Rubiolo
2005-04-04 11:06 ` Nick Clifton
2005-04-04 11:11 ` Dave Korn
2005-04-04 11:59 ` Sergei Organov
2005-04-04 13:39 ` Nick Clifton
2005-03-31 15:08 Zagorodnev, Grigory
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=13ab0c503312082c7af572c83f523f4f@powerescape.com \
--to=pieter@powerescape.com \
--cc=binutils@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).