Re: [Gumstix-users] Understanding gcc output code

[Pablo Y. T. <sh...@sa...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dave

thanks for the answer

Dave Hylands さんは書きました:
> 
> You'll be less frustrated if you disassemble a completely linked
> program, rather than just an object file.
> 
> What you'll find is that the divide is actually being performed by a
> helper function, called something like __aeabi_idiv

you're right, I didn't thought about it ;) while writting my one microkernel I had lots of unresolved symbols errors
(always such helper functions) until I found the right ld options. I've should have thought of that.

> 
> fp is short for "frame pointer".
> 
> Here's some good information about how call stacks (and frame
> pointers) typically work:
> <http://en.wikipedia.org/wiki/Call_stack>

thanks, that looks great. Does it applay to any function that is generated by gcc? Do gcc-generated function always
expect a correct fp register?


Pablo

- --
Pablo Yanez Trujillo
http://www.sakuranohana.org
My public key: http://www.sakuranohana.org/gpg/shaoran.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknwPbEACgkQDzf8xo+0xRVyRgCdH6Cw083bAPEZKs2ZbPxy1h5n
gsAAoIWq5srMhxLqE9Wmy7Z8y1bTuTop
=NJGd
-----END PGP SIGNATURE-----