From: Kevin Du Huanpeng <u74147@gmail.com>
To: barebox@lists.infradead.org
Subject: barebox.lds.S, why _edata not follows the end of .data section?
Date: Mon, 14 Oct 2013 21:02:49 +0800 [thread overview]
Message-ID: <CANvTkNZOQZt=XcYxSPX0+jT7tK9PrradDwWEcTtCfOQi1c9boQ@mail.gmail.com> (raw)
Hi, in the linker script,
> _sdata = .;
>. = ALIGN(4);
> .data : { *(.data*) }
? why _edata is not here?
> . = .;
> __barebox_cmd_start = .;
> .barebox_cmd : { KEEP(*(SORT_BY_NAME(.barebox_cmd*))) }
> more....
> __dynsym_start = .;
> *(.dynsym)
> __dynsym_end = .;
> }
> _edata = .;
> . = ALIGN(4);
> __bss_start = .;
why _edata is there?
other sections between _sdata and _edata, are they needed to be modified?
duhuanpeng
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-10-14 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 13:02 Kevin Du Huanpeng [this message]
2013-10-14 13:48 ` Alexander Aring
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='CANvTkNZOQZt=XcYxSPX0+jT7tK9PrradDwWEcTtCfOQi1c9boQ@mail.gmail.com' \
--to=u74147@gmail.com \
--cc=barebox@lists.infradead.org \
/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