- This topic has 11 replies, 2 voices, and was last updated 9 years, 3 months ago by Halle Winkler.
October 16, 2013 at 11:19 pm #1018654
Any timetable you can comment on for an arm64 slice to the framework? I’m working to add speech recognition to my app(s) and this is one of the few frameworks left I need to support arm64 and the iPhone 5s (And presumably the new iPad here next week).
Thanks for the response!
WesOctober 17, 2013 at 8:02 am #1018656
Good question. I only just received my long-ago-ordered 5S yesterday (OpenEars has to be tested for 64-bit compatibility on a real device since a fair amount of its important code isn’t used on the Simulator), so this is the next issue up after the upcoming 1.6 release that is currently in testing. Exact timeframes aren’t possible but I know it’s important to get out ASAP.October 17, 2013 at 12:13 pm #1018659
Just for clarity’s sake, having an arm64 slice isn’t necessary in order to support those devices, just to support them with 64-bit width. To create apps for arm64 devices that run 32-bit code, it is only necessary to remove arm64 from the architectures entry in your Xcode build settings. There are many libraries which either don’t have a 64-bit version out yet because (like OpenEars) they couldn’t test against the Simulator and aren’t based in the US so couldn’t take advantage of greater supplies of the 5S, or may not for a long time since iOS isn’t one of their important build targets or they don’t want to drop support for older iOS versions (this is an issue for me, since defaulting to arm64 support will mean cutting off two entire major versions that I otherwise have decided to support).
But as I said, I appreciate that everyone wants to support arm64 soon and I do as well.October 17, 2013 at 3:06 pm #1018665
Thanks for the response and congrats on your new iPhone 5S!
Yes, agreed on all points. I could remove arm64 from the valid architectures list and release, however, here’s my reasons for supporting the arm64 slice:
– All current and future high-end iPhones and iPads (maybe even the mini at some point) will be using the new 64-bit chip.
– 64-bit uses the the new, redesigned 64-bit iOS frameworks. Object creation is about half the time and there are many fixes (read fixed memory leaks) here still affecting the 32-bit frameworks.
– If your app supports 64-bit, iOS doesn’t have to load in the 32-bit framework. This give more memory availability to your app.
– My app deals with heavy real-time video processing from multiple sources. The performance boost I’m seeing with arm64 is very significant.
– My user base is already at > 75% iOS7. iOS 5 is less than 2%. My next app update will only support iOS 7. Older users can always download the latest available for their device. But any new features (like voice) will be an iOS 7 only feature for my app.
I do use a host of other libraries where most have converted to offering an arm64 slice (however, I am still waiting on one other library to make the conversion). I’ve seen these other libraries do it a multitude of ways. Some have found a way to support back to 4.3 in one library.a file. Other’s have opted to release 2 frameworks, one that targets iOS 5 and below and another that targets iOS 6 and up (including arm64).
With arm64, there are some great reasons to support it, but I do sympathize and agree that supporting a new slice with the backwards compatibility restrictions can be difficult.
Thanks for all that you do. I’ve been playing with the demos (including Rejecto) and I’ve VERY impressed with what this on-device speech recognizer can do and I’m really looking forward to offering this as an upsell feature to my apps.
WesOctober 17, 2013 at 3:45 pm #1018666
We’re in complete agreement; your points are 100% on the money and I’m actually looking forward to seeing if there are new features that can be supported that will take advantage of the strengths of the new architecture as it becomes more mainstream. I wanted to clarify just so that someone else reading this discussion doesn’t think they can’t make an app for the 5S at all yet, and to head off potentially having to answer that misconception in other channels. Thank you for your kind words!October 17, 2013 at 5:11 pm #1018667
Agreed. arm7/7s/32-bit still works on the iPhone 5S. However, taking the time to convert to arm64 really impressed me with how easy it was to do (maybe 2 days tops) and the performance gains I got from running native 64-bit code on the new iPhone.
Hopefully the OpenEars code base won’t give you too much trouble to compile as arm64.
WesOctober 17, 2013 at 5:21 pm #1018668
I would be surprised if it were easy or fast, since the amount of source which is potentially affected and has to be cleared as working as expected is in the multiple hundreds of individual source files, or more than a thousand files including the plugins. Realistically, it is going to take some time to do properly.October 17, 2013 at 5:59 pm #1018669
No argument here. I’m sure every project will be different. Here were my stats:
Main app source:
400+ source files
COTS library to support real-time video streaming decoding (I have to compile this on my own):
Thousands of source files
??? LOC. Easily 400k+ LOC
I didn’t find any issues with the wider bit definitions for integers, etc. In fact I could have just done a recompile and left the hundreds of warnings in place and the app worked perfectly. The majority of the time spent was cleaning up the warnings (mostly NSInteger casting).
Now, if you are doing some intense bit shifting work where you need to detect the end of the 32-bit register, then I could see where moving to 64 might cause you some headaches.
Hopefully it won’t be too bad for you; I’m sure every project will have a different experience.
Good luck! (and I’m eagerly anticipating arm64 support :)
WesOctober 17, 2013 at 6:01 pm #1018670
Thanks!December 12, 2013 at 10:03 pm #1019146
Well, that turned out to be extremely difficult but 64-bit is now out for OpenEars and all of its plugins at https://www.politepix.com/openearsDecember 16, 2013 at 7:04 pm #1019179
Great work Halle!
I’m checking it out now and at first glance it appears to be more snappy and is doing a better job at recognizing speech.
I’m now moving forward on integrating this with my app. Again, great job. I’m sure the arm64 conversion wasn’t too much fun.
WesDecember 19, 2013 at 10:51 am #1019211
- You must be logged in to reply to this topic.