Hacker News Reader

This is not about Linux. Every brittle OS on ARM uses the standard ABIs. But Apple can't? Gimme a break.

Apple's ABI for iOS is a custom derivative of APCS, not AAPCS. They do not even try to conform to the AAPCS ABI, nor should they need to. iOS has a soft-float ABI, but uses the float glue names from libgcc, not the EABI names.

This whole thing reads like the LuaJIT guy whining that he has to do some work to port to iOS. The compiler-rt library provides these functions and it shouldn't take him more than 10 minutes to figure out the proper names to use on iOS.

Just so you know, it's the "LuaJIT guy" that you're replying to there.

That doesn't mean that ohmantics here doesn't have a good point (that it's not realistic to assume that porting to the different platforms doesn't involve some work specific to the platform) and gives the precise information where the soft-float functions on iOS can be found.

I can also understand Mike too that he didn't want to spend the time on that port (I think, because iOS doesn't allow apps any Jiting, thereby limiting the power of LuaJit on iOS). Still the information that ohmantics gives regarding compiler-rt library can help us obtain a balanced view.

I don't understand the problem. Did they not document their ABI?

Reply on news.ycombinator.com