Re: making the most of a symbolic breakpoint
Re: making the most of a symbolic breakpoint
- Subject: Re: making the most of a symbolic breakpoint
- From: Kyle Sluder <email@hidden>
- Date: Wed, 09 Jan 2013 12:54:55 -0800
On Wed, Jan 9, 2013, at 12:22 PM, Greg Parker wrote:
>
> Look for the iOS ABI Function Call Guide.
>
> http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/iPhoneOSABIReference/Articles/ARMv6FunctionCallingConventions.html
> http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/iPhoneOSABIReference/Articles/ARMv7FunctionCallingConventions.html
Ah, thank you! I don't know why I was so incapable of finding these
documents on my own.
On Wed, Jan 9, 2013, at 12:33 PM, Greg Parker wrote:
>
> Without heroic measures, a true ABI break means either "your old apps
> don't work" or "there are two copies of the OS shared library stack in
> memory". The sub-optimal parts of our ARM ABI aren't bad enough to
> justify that cost.
Why should iOS devs miss out on the magic of Universal Procedure
Pointers? :)
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden