arm-none-eabi-gcc displaces zero-valued .data into .bss

OP #3173229
I'm using a fairly current yargarto on a slightly older MacOS.  Specific 
details should be extractable from output.sh.

As I understand the distinction between linker sections .data and .bss:
- initialised data goes in .data
- uninitialised data goes in .bss
- data that goes in .bss is not guaranteed to be zero-valued

I think that my test shows that this version of gcc is putting:
- non-zero valued data in .data
- zero-valued data in .bss

Do people think that this is a fault?
Attached files:
Moderator #3173517
James C. wrote:

> - data that goes in .bss is not guaranteed to be zero-valued

No.  Data in .bss are supposed to be zeroed out at startup by the
run-time startup code.  .data is meant for data being initialized
to non-zero values.  On microcontrollers, this is typically done
by copying over their initial values from flash (again, by the
run-time startup code).

Reply

A question of your own? This thread is over 13 years old. Ask it in a thread of its own – more people read along there, and it gets answered more often and sooner.

Start a new thread

A fix, an addition or feedback on this thread? Then reply here.

Formatting
  • [c]C-Code[/c]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]
  • [[Title]] – link to an article
  • Link to another post: right-click its post ID (#8078628), copy the address, paste it into the text

More about formatting

Post long source code as an attachment, not in the text.

Already registered? Log in

Not shown to anyone. We send you a link; your post appears once you confirm it there.

By submitting you create a free account and accept the terms of use.