It fucking does. Y'all don't give @davejmurphy enough credit, as far as I can tell devkitppc is the last maintained open source ppc toolchain left and it was for console hacking memes.https://twitter.com/hedgeberg/status/1012226738267545600 …
-
Just looked at the diff again and "s32/u32" went from being typedef "[unsigned] int" to typedef "long [unsigned] int". Not sure if that caused the aforementioned breakage, but that change alone was a major pain in the ass since it spewed warnings for basically every printf.pic.twitter.com/9kRdlhlgpj
And yes I know both are 32 bits on this platform, but that doesn't mean they're freely interchangeable. And this isn't the only issue; basically every HBC release we've had where we updated libogc/devkitPro at the same time, we had to fix *some* breakage.
-
-
Well *exactly* Marcan. It doesn't mean they're freely interchangeable and the warnings you refer to are because of somebody's code being written as if they are.
-
You mean "everybody's". This is platform-specific code. The convention for the libogc APIs is to return s32. There's no printf specifier for s32. There is one for int32_t (if you assume *that* mapping never changes), but who uses PRId32 for every single return code?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.