RE: [ECOS] compile error when using newer version ecos configurat ion tool

RE: [ECOS] compile error when using newer version ecos configurat ion tool

[Fabrice Gautier]

> 
> PS. What does BSS stand for anyway? Answers on a post card please.
> 

I actually think I know that, but I don't have any postcard, sorry...

A+

Fabrice

-- 
Fabrice Gautier, 
Fabrice_Gautier@sdesigns.com

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[Andrew Lunn]

On Mon, Nov 12, 2001 at 12:59:48PM -0800, Fabrice Gautier wrote:
> 
> > 
> > PS. What does BSS stand for anyway? Answers on a post card please.
> > 
> 
> I actually think I know that, but I don't have any postcard, sorry...

Thats OK. I went hunting and found a definition. Blank Static
Storage. Took some finding. Its one of the acronyms which everyone
uses but few people actually know what is stands for.

     Andrew

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[David Airlie]

> >
> > I actually think I know that, but I don't have any postcard, sorry...
>
> Thats OK. I went hunting and found a definition. Blank Static
> Storage. Took some finding. Its one of the acronyms which everyone
> uses but few people actually know what is stands for.

Block Started by Symbol was one I heard once before ... some IBM assembler
one .. your one sounds better...

Dave.

>
>      Andrew
>

-- 
      David Airlie, Software Engineer, Parthus Technologies plc.,
       Mary Rosse Centre, National Tech Park, Limerick, Ireland.
   t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[jf simon]

> >
> > I actually think I know that, but I don't have any
postcard, sorry...
>
> Thats OK. I went hunting and found a definition. Blank
Static
> Storage. Took some finding. Its one of the acronyms
which everyone
> uses but few people actually know what is stands for.
>

I found another one:
BSS: Block started by Symbol ( IBM 7090 assembly
directive... very old) . From "The design of the Unix
system" MJ. Bach
-jfs

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[Alex Schuilenburg]

Andrew Lunn wrote:

> On Mon, Nov 12, 2001 at 12:59:48PM -0800, Fabrice Gautier wrote:
> 
>>>PS. What does BSS stand for anyway? Answers on a post card please.
>>>
>>>
>>I actually think I know that, but I don't have any postcard, sorry...
>>
> 
> Thats OK. I went hunting and found a definition. Blank Static
> Storage. Took some finding. Its one of the acronyms which everyone
> uses but few people actually know what is stands for.


I asked the compiler folks around here.  The answer I got was that
  "bss" was actually the mnemonic for the IBM/370 instruction that
zero'ed a section of memory, and hence how the naming of the section was derived.

No-one can recall what the mnemonics actually stood for though - not old enough ;-)

-- Alex

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[Alex Schuilenburg]

Alex Schuilenburg wrote:
...

> I asked the compiler folks around here.  The answer I got was that
>  "bss" was actually the mnemonic for the IBM/370 instruction that
> zero'ed a section of memory, and hence how the naming of the section was 
> derived.
> 
> No-one can recall what the mnemonics actually stood for though - not old 
> enough ;-)


Correction :-)

It was a PDP10 instruction and not an IBM/370 as originally reported
and it really stands for:

         Block Started By Symbol.

As reported by "jf simon" <jfsimon@mageos.com>

Clear as mud really...

-- Alex

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[Chris Gray]

Alex Schuilenburg wrote:

> I asked the compiler folks around here.  The answer I got was that
>   "bss" was actually the mnemonic for the IBM/370 instruction that
> zero'ed a section of memory, and hence how the naming of the section was derived.
>
> No-one can recall what the mnemonics actually stood for though - not old enough ;-)

I'd better not admit to having a 360 assembler manual at home then ...

My favourite ASM/360 instruction was the one to set memory to BCD
zero: Zero and Add Packed, it was called. :)

Chris

RE: [ECOS] compile error when using newer version ecos configurat ion tool

[Patrick Doyle]

> My favourite ASM/360 instruction was the one to set memory to BCD
> zero: Zero and Add Packed, it was called. :)
>
I used to work with the TMS32020 DSP from TI (about 15 years ago).  My
favorite instruction on that processor was the XOR with a Konstant
instruction... spelled XORK :-)

--wpd

Re: [ECOS] BSS [was compile error when using newer version ecos configurat ion tool]

[Tommy Reynolds]

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

It was a dark and stormy night.  Suddenly
"Chris Gray" <chris.gray@acunia.com> began to type furiously:

> Alex Schuilenburg wrote:
> 
> > I asked the compiler folks around here.  The answer I got was that
> >   "bss" was actually the mnemonic for the IBM/370 instruction that
> > zero'ed a section of memory, and hence how the naming of the section was derived.
> >
> > No-one can recall what the mnemonics actually stood for though - not old enough ;-)

Well, I qualify for this one ;-)

Back in the olden days when everything was written in assembly language,
evaluating arithmetic expressions was really hard; that's why FORTRAN originally
constrained array subscripts to look like "n*k+i": you could leave out parts but
if present, they must be written in this order.

Anyway, writing in assembly language itself was a bit of a challenge because the
assembler didn't allow expressions just anywhere.  Where today, you'd write
something like:

	MyLabel: . = . + 500

to reserve some memory, the assembler had to provide a special opcode:

	MyLabel bss 500

that defined "MyLabel" as a "block started by symbol" and "MyLabel" was
addressed as the first location in the memory area.  There was also a "BES" that
was "block ended by symbol":

	MyLabel bes 500

that assigned "MyLabel" to the last (last + 1? I don't remember) location of the
block.

Thank goodness that everything is not a special case these days.

Cheers!

---------------------------------------------+-----------------------------
Tommy Reynolds                               | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone:  +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA  | FAX:    +1.256.837.3839
Senior Software Developer                    | Mobile: +1.919.641.2923

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [ECOS] compile error when using newer version ecos configurat ion tool

[Andrew Xiang]

I am running ecos on assabet.
I have redboot running, I compiled the simple printf("hello"); program 
accroding to the manual.
and try to run it on both gdb and download to board, I don't see the 
hello get printed?
Also tried the twothreads.c with no luck.

Since I have the console through the serial port, do I have to tell it 
to print to the serial port?
What am I doing wrong?

thanks
Andrew

[ECOS] printf does not work, why?

[Andrew Xiang]

I am running ecos on assabet.
I have redboot running, I compiled the simple printf("hello"); program 
accroding to the manual.
and try to run it on both gdb and download to board, I don't see the 
hello get printed?
Also tried the twothreads.c with no luck.

Since I have the console through the serial port, do I have to tell it 
to print to the serial port?
What am I doing wrong?

thanks
Andrew

RE: [ECOS] compile error when using newer version ecos configurat ion tool

[Richard Panton]

> > My favourite ASM/360 instruction was the one to set memory to BCD
> > zero: Zero and Add Packed, it was called. :)
> >
> I used to work with the TMS32020 DSP from TI (about 15 years ago).  My
> favorite instruction on that processor was the XOR with a Konstant
> instruction... spelled XORK :-)

And of course, the wonderful 6809 processor, the only time I've seen the
(S)ign (EX)tend op-code with a truely memorable mnemonic:
   http://www.geocities.com/siliconvalley/heights/1681/6809.HTM >;-)

RE: [ECOS] compile error when using newer version ecos configurat ion tool

[Jeremias, Thilo]

I think, ANSI-C, specifies that ALL non automatic vars, are implicitly
initialised to zero (that's BSS).
Automatic var s like (locals) contain garbage!

It's probably a religious discussion wether this is good or bad,
but IMHO I would always explicitly initialise anything I use.

-----Original Message-----
From: Trenton D. Adams [mailto:tadams@theone.dnsalias.com]
Sent: Wednesday, 14 November 2001 12:47
To: 'J. J. Farrell'
Cc: 'Andrew Lunn'; 'eCos'
Subject: RE: [ECOS] compile error when using newer version ecos
configuration tool


So, what you're saying is that BSS is infact for uninitialized
variables?  Because of the fact that the BSS section is initialized to
0, the uninitialized variables become initialized?

> -----Original Message-----
> From: J. J. Farrell [mailto:jjf@abaqos.com] 
> Sent: November 13, 2001 4:54 PM
> To: Trenton D. Adams
> Cc: 'Andrew Lunn'; 'eCos'
> Subject: Re: [ECOS] compile error when using newer version 
> ecos configuration tool
> 
> 
> On Tue, Nov 13, 2001 at 02:46:52PM -0700, Trenton D. Adams wrote:
> >
> > 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.
> > 
> > > From: Andrew Lunn [mailto:andrew.lunn@ascom.ch]
> > > 
> > > 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!
> 
> I think you're misinterpreting things here. gcc can be 
> configured to output for any number of different assemblers 
> and output formats, and -fno-common is applicable to many of 
> them - it has nothing in particular to do with ELF.
> 
> -fno-common is concerned with controlling object linkage - 
> whether an external variable declared in more than one source 
> file results in a single object, or multiple objects with the 
> same name. It has nothing directly to do with initialization.
> 
> C global variables which are not explicitly initialized must 
> be initialized by the compiler/linker/loader as if 0 had been 
> assigned to them. This is often achieved by describing them 
> in a .bss section without any initialization, then having the 
> loader initialize the .bss section to 0 when it loads the program.
> 

RE: [ECOS] compile error when using newer version ecos configurat ion tool

[Fabrice Gautier]

> 
> PS. What does BSS stand for anyway? Answers on a post card please.
> 

I actually think I know that, but i don't have any postcard, sorry...

A+