Message 232209 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	vstinner
Recipients	neologix, njs, pitrou, rhettinger, tim.peters, vstinner
Date	2014年12月05日.21:20:21
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1417814421.42.0.36851356357.issue18835@psf.upfronthosting.co.za>

Content
Windows provides: void * _aligned_malloc( size_t size, size_t alignment ); http://msdn.microsoft.com/en-US/library/8z34s9c6%28v=vs.80%29.aspx How should we handle platforms which don't provide a memory allocator with an alignment? The simplest option is to return NULL (MemoryError). Allocating more memory and skip first bytes may work, but how do we retrieve the original address if the function releasing the memory block? What about Solaris, Mac OS X, FreeBSD, etc.

Content

Windows provides:
void * _aligned_malloc(
 size_t size, 
 size_t alignment
);
http://msdn.microsoft.com/en-US/library/8z34s9c6%28v=vs.80%29.aspx
How should we handle platforms which don't provide a memory allocator with an alignment? The simplest option is to return NULL (MemoryError).
Allocating more memory and skip first bytes may work, but how do we retrieve the original address if the function releasing the memory block?
What about Solaris, Mac OS X, FreeBSD, etc.

History
Date	User	Action	Args
2014年12月05日 21:20:21	vstinner	set	recipients: + vstinner, tim.peters, rhettinger, pitrou, njs, neologix
2014年12月05日 21:20:21	vstinner	set	messageid: <1417814421.42.0.36851356357.issue18835@psf.upfronthosting.co.za>
2014年12月05日 21:20:21	vstinner	link	issue18835 messages
2014年12月05日 21:20:21	vstinner	create

homepage