The following is a PDF on AAPCS (eabi calling conventions)
http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042d/IHI0042D_aapcs.pdf
This describes a little about the differences and the linux port for eabi:
http://wiki.debian.org/ArmEabiPort
Android should use the same calling conventions as it also uses ARM EABI. I haven't been able to test this on android, as I haven't been able to get angelscript to compile. The android NDK is missing a lot of stuff, including a real stdc++ library. I'm guessing who ever ported it used one of the third-party toolchains to build it. But I'm really curious if these tests pass on it or not.
jeremy
Test case fails on armel
Android does have a stdc++ library and much better support for C++ in NDK r5. I'm working to get the library and test_feature built and will post the results when I'm done.
After a long time rooting my phone (which required me to downgrade then upgrade again), and figuring out all the correct flags, and include paths I got test_feature to compile. The GetSet test actually causes a segfault on my phone, I will try to figure out where it crashes, just need to figure out how to use gdb with my phone. Skipping that test leads to the same failure in test_scriptstring.
I believe the original code for arm was written for embedded devices, so it may not follow the ABI used by Linux and Android.
I'll study the specification for the ABI and see if I can determine what exactly needs to be modified. Unfortunately I do not have any ARM devices so I can't really test any of the changes myself.
I'll study the specification for the ABI and see if I can determine what exactly needs to be modified. Unfortunately I do not have any ARM devices so I can't really test any of the changes myself.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement