Greetings! 
Since libtonc was updated to 1.4.5 (specifically this commit). The type tonc uses for s32/u32 has changed to using stdint.h types "int32_t"/"uint32_t" which is implemented as "long int" and "long unsigned int". This is from stdint.h from arm-none-eabi-gcc provided with devkitARM. My projects started to break after updating to the recent pacman upgrades. 
I made a PR for grit here. Be nice to get this into the pacman releases to keep that ecosphere running good. 
grit didn't output s32/u32 types, you shouldn't have been using those types to access data added via grit. This is a bug in your code, it isn't a mismatch between libtonc and grit.
Hey, I understand that grit doesn't use tonc types, but I don't think it's out of reason to assume that when grit outputs a tile array, that it would match with the same types tonc expects. The issue is that tonc's u32/s32 are now considered "long int" since v1.4.5 released. I made the PR to fix issues with grit outputting "unsigned int" where tonc expected "unsigned long". But, this issue only is one of many from that change. For example, when building tonc-examples, I see that the FIXED type is now "long int" causing some projects not to build. Error for that here: https://pastebin.com/w3r8R3c1 .
Not sure how deep this would go, but I do think that commit I linked for tonc should be reverted in the meantime.
This is clearly an error in the example code though. You shouldn't prototype functions with one type and then implement them with another
Users browsing this forum: No registered users and 1 guest