[ECOS] compile error when using newer version ecos configuration tool
Trenton D. Adams
Sun Nov 4 11:02:00 GMT 2001
I think you're correct! Why because the -fno-common option to GCC
specifies that it will allow uninitialized data to be put in the bss
section. Which indicates to me that it's not normal for ELF.
I don't have much documentation on this so I can't confirm for sure.
I'll take you're word for it! ;)
> -----Original Message-----
> From: Andrew Lunn [mailto:email@example.com]
> Sent: November 13, 2001 1:28 AM
> To: Trenton D. Adams
> Cc: 'eCos'
> Subject: Re: [ECOS] compile error when using newer version
> ecos configuration tool
> On Mon, Nov 12, 2001 at 02:46:38PM -0700, Trenton D. Adams wrote:
> > I don't know what it stands for, but I know what it's used for.
> > Here's a quote from a Technical Article from MSDN which should be
> > relevant since bss is the same for ELF binaries as it is
> for PE binaries
> > as far as I know! :)
> > The size of the sections that the loader commits space for in the
> > virtual address space, but that don't take up any space in the disk
> > file. These sections don't need to have specific values at program
> > startup, hence the term uninitialized data. Uninitialized
> data usually
> > goes into a section called .bss.
> Off topic but...
> It seems the ELF spec specifies the .bss section is initialized to
> zero. Where as what you say about PE is that the contents are not
> initialized. Something to remember when writing portable code!
More information about the Ecos-discuss