Newlib, syscall.c and printf
Wed Feb 9 21:09:00 GMT 2011
-----BEGIN PGP SIGNED MESSAGE-----
On 02/09/2011 12:47 PM, Hard Maker wrote:
> If they don't have the right value, that's the problem.
> This work fine. But I suspect about the stack setup or linker script.
> When I build the aplication if stack space grows, the applicacion grows
> too. Using 64 bytes of stack, the application is 49652 bytes long. When
> the stack is 8192 bytes, the application size is 82164 byte. This is ok?
> I'm not sure, as I see the only diference is the size used in ram, there
> are not diference in application code. But I don't have experience using
> arm or newlib.
I'm assuming you're reporting the output of arm-eabi-size called on your
This should not happen. Application size should grow only when
- - more code is added, either by writing new functions or calling
functions in libraries like newlib. This increases .text
- - more initialized static/global variables are added.
This increases the copy of .data
Maybe you'd want to have a look at my linker script for stm32:
I't a bit complex because it has to support C++ as well as C, and is
designed for an OS kernel, but you might find it useful.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Newlib