public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Why are some global vars part of the image, and some not?
Date: Mon, 06 Nov 2006 14:06:06 -0500	[thread overview]
Message-ID: <454F879E.9020803@smiths-aerospace.com> (raw)
In-Reply-To: <454F854B.9000402@freescale.com>

Scott Wood wrote:
> Jerry Van Baren wrote:
>> In theory, yes.  In practice, I have my doubts that it is workable, let 
>> alone a better way.  Writing "then the compiler would be the one that 
>> zeros BSS" is easy, actually making it work may be tricky.
> 
> It's a pretty simple linker script change, actually.  Just move all of 
> the lines within .bss {} into .data {}.  Where do you see the difficulty 
> coming from?
> 
> -Scott

Does the linker create proper zero initialization?  If you initialize a 
variable to zero, the compiler puts it in bss and does not initialize 
it, secure in the knowledge that the runtime zeroes bss.  If you 
subsequently put it in the data section via the linker script, does it 
get zeroed?

Does the bss/data end up in the right place?  On start up your stack is 
in cache or dual-port RAM until SDRAM is initialized.  When does the 
initialized portion of the data section get initialized and where? 
Before it is in SDRAM or after SDRAM is initialized?

Simple enough things to experiment with, but it all takes time and the 
benefit is questionable.  Feel free to prove us curmudgeons wrong. ;-)

gvb

  reply	other threads:[~2006-11-06 19:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 21:58 [U-Boot-Users] Why are some global vars part of the image, and some not? Timur Tabi
2006-11-03 22:19 ` Timur Tabi
2006-11-03 23:47   ` Wolfgang Denk
2006-11-04  0:09     ` Timur Tabi
2006-11-04  0:33       ` Wolfgang Denk
2006-11-03 23:44 ` Wolfgang Denk
2006-11-04  0:07   ` Timur Tabi
2006-11-04  0:31     ` Wolfgang Denk
2006-11-04  1:38       ` Timur Tabi
2006-11-04  2:04         ` Wolfgang Denk
2006-11-06 17:43           ` Scott Wood
2006-11-06 18:03             ` Jerry Van Baren
2006-11-06 18:08               ` Timur Tabi
2006-11-06 18:48                 ` Jerry Van Baren
2006-11-06 18:56                   ` Scott Wood
2006-11-06 19:06                     ` Jerry Van Baren [this message]
2006-11-06 19:46                       ` Scott Wood
2006-11-06 19:54                         ` Timur Tabi
2006-11-06 20:13                         ` Jerry Van Baren
2006-11-06 20:21                           ` Timur Tabi
2006-11-06 20:44                             ` Wolfgang Denk
2006-11-06 20:35                         ` Tolunay Orkun
2006-11-06 20:29                 ` Wolfgang Denk
2006-11-06 20:26             ` Wolfgang Denk
2006-11-06 20:48               ` Scott Wood
2006-11-06 21:15                 ` Wolfgang Denk

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=454F879E.9020803@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.com \
    --cc=u-boot@lists.denx.de \
    /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