This is 6 months old on a version of XCode that is now two versions out of date. Is there a reason it's being brought up now?
Is there a reason it's being brought up now?
Flamebait.
LuaJIT maintainer's take on Apple/Clang
21–27 of 27 posts
Re: LuaJIT maintainer's take on Apple/Clang
#22Earlier quoted context omitted.
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…
Just so you know, it's the "LuaJIT guy" that you're replying to there.
Re: LuaJIT maintainer's take on Apple/Clang
#23Apple is actively trying to fix this problem. If you know any talented compiler gurus who want to work at Apple, you could refer them. [0][1] . [0] "LLVM Backend Compiler Engineer" http://jobs.apple.com/index.ajs?BID=1&method=mExternal.s... [1] "LLVM Backend Compiler Engineer" http://jobs.apple.com/index.ajs?BID=1&method=mExternal.s...
I would recommend people don't work for Apple. It's one thing to lie about computing history and say you invented everything so that customers believe it and give you lots of money (which you then use to outsource jobs and stop the company charity program) it's another thing entirely to drink your own kool-aid and start a series of the most embarrassing lawsuits I've ever seen. Apple is now officially not just a dodg…
I think regardless of the lies, they had a superior operating system up until Lion. Now their business practices and complete disregard for their developers' comfort is fairly inexcusable. Nor do I like the draconian systems of the App Stores.
Re: LuaJIT maintainer's take on Apple/Clang
#24The LuaJIT maintainer is missing that Apple does not claim any conformance to ARM EABI. Apple's ABI is defined to be based on the AAPCS standard, but Apple makes no claims to it being exact. In other words, it's not Linux, and it sounds like the LuaJIT maintainer is annoyed that it doesn't follow a common approach used on Linux. Anyone that works on low-level implementations that sit below the standard platform compi…
This is not about Linux. Every brittle OS on ARM uses the standard ABIs. But Apple can't? Gimme a break.
I don't understand the problem. Did they not document their ABI?
Re: LuaJIT maintainer's take on Apple/Clang
#25Earlier quoted context omitted.
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…
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.
Re: LuaJIT maintainer's take on Apple/Clang
#26Apple is actively trying to fix this problem. If you know any talented compiler gurus who want to work at Apple, you could refer them. [0][1] . [0] "LLVM Backend Compiler Engineer" http://jobs.apple.com/index.ajs?BID=1&method=mExternal.s... [1] "LLVM Backend Compiler Engineer" http://jobs.apple.com/index.ajs?BID=1&method=mExternal.s...
I would recommend people don't work for Apple. It's one thing to lie about computing history and say you invented everything so that customers believe it and give you lots of money (which you then use to outsource jobs and stop the company charity program) it's another thing entirely to drink your own kool-aid and start a series of the most embarrassing lawsuits I've ever seen. Apple is now officially not just a dodg…
Well, Apple's stock has increased massively over the past few days of the trial between Apple and Samsung, so the shareholder's can't think it's "embarrassing". Looking at the share price, I'd have thought the shareholders think its going quite well, especially when you think that they didn't have an especially good quarter.
Re: LuaJIT maintainer's take on Apple/Clang
#27This is 6 months old on a version of XCode that is now two versions out of date. Is there a reason it's being brought up now?
No there's no reason to bring this up now. First, it has been worked around and second, VFP support for the LuaJIT ARM port is already in progress (parts are in the git repo, not enabled yet).
What is the work-around? I'm trying to get luajit working on iOS 6+ on ARMv7 and above...