According to Apple, this is in fact the case. <http://developer.apple.com/technotes/tn2005/tn2130.html>
And you might find the following of interest. <http://developer.apple.com/documentation/Performance/Conceptual/ ManagingMemory/Articles/MemoryAlloc.html> Charles Yeomans On Apr 20, 2007, at 12:23 AM, Frank Condello wrote: > I'm pretty sure NewPtr calls down to malloc eventually (in newer > versions of OS X at least) but it might do some other nasty stuff for > backwards compatibility. Regardless, I don't foresee ever needing > allocations of that size - I just need guaranteed alignment. > > Frank. > <http://developer.chaoticbox.com/> > <http://macgameblog.com/> > > On 19-Apr-07, at 10:01 PM, Peter K. Stys wrote: > >> I believe NewMemoryblock uses Apple's NewPtr call so you can check >> there (I had a problem with 1GB block limits and this was the reason; >> malloc has no such limit, or at least 2-4GB, ASFAIK) >> >> Peter. >> >> On 4/19/07, Frank Condello <[EMAIL PROTECTED]> wrote: >>> I've started declaring into Accelerate.framework and have read that >>> Mac OS X's malloc always uses 16-byte alignment, but I was wondering >>> if I could rely on this alignment from an RB-supplied MemoryBlock. I >>> know this has been discussed before but I couldn't find a definitive >>> yes or no - I suspect (and hope) the answer is yes, if not, I've got >>> a bit more work to do! >>> >>> TIA, >>> Frank. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
