Marmalade: Angelscript runs fine on x86, crashes on ARM

UltimateWalrus · 2012-12-19T21:27:09

Hello, I am making a mobile game engine that runs on TinyXML and Angelscript. I'm using MSVC 2010 Professional. I used the Marmalade Angelscript project found in this thread and it seems to be working. So far, I've made it so I can define hierarchical game objects and their properties in XML, and optionally reference Angelscript scripts that specialize the functionality even further. Angelscript looks very promising, and while there've been a few hiccups I couldn't find reference to in the documentation, the library seems to be designed sensibly enough that with enough persistence I can usually figure out what's wrong. Now, however, I'm completely stuck. I suspect the issue may lie with Marmalade as much as Angelscript. The engine runs flawlessly when I compile to x86 and run it in the Marmalade simulator. However, when I want to compile to ARM so I can run on an iOS device, something bad happens and it crashes. I stepped through in the ARM simulator and found the game was blowing up whenever I tried to register a function for Angelscript. Upon further inspection, I saw the AS_MAX_PORTABILITY #define was getting set, making it so I can only use the "generic" calling convention. I haven't written a lot of cross-platform code so I'm a newbie to thinking about different calling conventions, but from searching it looks to me as if ARM is supposed to be able to use CDECL function calls just fine. Using #pragma messages I figured out where AS_MAX_PORTABILITY was getting defined. It's here in as_config.h: #if (!defined(AS_X86) && !defined(AS_SH4) && !defined(AS_MIPS) && !defined(AS_PPC) && !defined(AS_PPC_64) && !defined(AS_XENON) && !defined(AS_X64_GCC) && !defined(AS_X64_MSVC) && !defined(AS_ARM) && !defined(AS_X64_MINGW)) #ifndef AS_MAX_PORTABILITY #define AS_MAX_PORTABILITY #endif #endif AS_MARMALADE is defined, but I realized that AS_ARM should probably also be defined, so I tried setting that in the project properties. Unfortunately when I do that, along with some probably-harmless warnings about ignoring stdcall, I get compiler errors: 1> Debug_AngelScript_new_vc10_gcc_arm/as_callfunc_arm.obj: In function `CallSystemFunctionNative(asCContext*, asCScriptFunction*, void*, unsigned long*, void*, unsigned long long&)': 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(126) : undefined reference to `armFuncR0' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(130) : undefined reference to `armFunc' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(134) : undefined reference to `armFuncR0' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(142) : undefined reference to `armFuncR0R1' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(147) : undefined reference to `armFuncR0' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(155) : undefined reference to `armFuncR0R1' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(159) : undefined reference to `armFuncObjLast' 1> 1> 1> d:/sebastian/games/marmalade/angelscript_new3/angelscript_marmalade/angelscript/source/as_callfunc_arm.cpp(162) : undefined reference to `armFuncR0ObjLast' This doesn't make any sense, since the extern function definitions appear to be right there at the top of the document. I get that they reference assembler routines, but if anything went wrong there I would expect a linker error not a compiler error. I've fiddled around with as_config.h a little more but can't find the solution. I feel like I'm stuck, since going any further would require fiddling around with the Angelscript source, in a place where I don't really fully understand how it works. Are there any ideas of what I can do to get Angelscript to run correctly when built for ARM? I am doing this game as part of a small sponsorship deal so I am on a really tight schedule. Worst case scenario, I can kludge this milestone by "pretending" Angelscript is being used; however it looks as though Andreas Jönsson peruses these forums somewhat frequently so I thought posting would be a good idea. I feel a little guilty asking for quick help from the creator of a library that's already very graciously offered for free... You have my word that, if the game makes any money, I'll be sure to make a nice donation on the AngelCode site :] Thank you very much, Sebastian

AngelCode Affiliates

Started by UltimateWalrus September 24, 2012 04:45 PM

34 comments, last by WitchLord 11 years, 3 months ago

WitchLord

4,834

December 05, 2012 12:29 PM

Great. It looks like __S3E__ is a useful define to look for to identify Marmalade. With this it should no longer be necessary to manually define Marmalade anywhere. I3D_ARCH_ARM and I3D_ARCH_X86 etc will be used to determine for which CPU the library is compiled, and will control the code for the native calling conventions.

I'll make the necessary changes in the as_config.h, and let you know when it's checked in.

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

WitchLord

4,834

December 05, 2012 11:48 PM

I've checked in the changes in revision 1490.

It should no longer be necessary to make any defines to compile AngelScript for Marmalade. Please give it a try and let me know if there are any problems.

Based on the tests that UltimateWalrus had made, I configured Marmalade to use the same ABI as is used for Android. It's possible that later on you'll find some functions that don't work properly if this assumption is incorrect. If that happens, please tell me and I'll make the necessary changes in the library.

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Braden M

126

December 06, 2012 11:05 PM

Thanks Andreas! I really appreciate how responsive you are with fixes to AngelScript. I just tried out r1490 and it works perfectly as far as I can tell. I've put the new MKB in a separate branch for now, and I'll update "master" once 2.26 is released. The only "tweak" that I had to leave in was a definition of "fopen_s" that I put in preinclude.h, because Marmalade's standard library doesn't have that function available, even in Visual Studio.

Also, FYI, there are two compiler warnings that come up with Marmalade's ARM GCC4.4 (arm-none-eabi-g++); the first one looks like it could possibly affect bytecode output so I'll mention it in case you weren't aware of it.



angelscript/source/as_bytecode.cpp: In member function 'void asCByteCode::DebugOutput(const char*, asCScriptEngine*, asCScriptFunction*)':

angelscript/source/as_bytecode.cpp:2114: warning: format '%3d' expects type 'int', but argument 3 has type 'long unsigned int'





add_on/scripthelper/scripthelper.cpp: In function 'int WriteConfigToFile(asIScriptEngine*, const char*)':

add_on/scripthelper/scripthelper.cpp:194: warning: format '%X' expects type 'unsigned int', but argument 3 has type 'asDWORD'

The second warning occurs a total of ten times at different lines in scripthelper.cpp.

WitchLord

4,834

December 06, 2012 11:54 PM

Thanks, these last issues should now be fixed in revision 1493.

You should not need the fopen_s tweak anymore. I had forgotten a few places were I was using fopen_s. These are in either case only used when compiling the library in debug mode.

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Braden M

126

December 19, 2012 07:58 PM

Hi Andreas, I just found two more places where fopen_s is still causing that error even with the latest revision (if I omit the preinclude.h file) - both in add_ons:

scriptfile/scriptfile.cpp (line 320)
scripthelper/scripthelper.cpp (line 169)

WitchLord

4,834

December 19, 2012 09:27 PM

Thanks. I'll have these fixed the same way (by adding a check for #if defined(__S3E__))

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Marmalade: Angelscript runs fine on x86, crashes on ARM

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Marmalade: Angelscript runs fine on x86, crashes on ARM

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines