8000 Aligned allocator for numpy (Trac #568) · Issue #1166 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

Aligned allocator for nu 8000 mpy (Trac #568) #1166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
numpy-gitbot opened this issue Oct 19, 2012 · 7 comments
Closed

Aligned allocator for numpy (Trac #568) #1166

numpy-gitbot opened this issue Oct 19, 2012 · 7 comments

Comments

@numpy-gitbot
Copy link

Original ticket http://projects.scipy.org/numpy/ticket/568 on 2007-08-11 by @cournape, assigned to unknown.

Here is a first patch to have aligned allocator in numpy: this does not give yet a high interface to create arrays with a given alignment, only aligned allocators in the array interface.

The patch:

  • defines aligned allocators
  • Make PyDataMem_* macro to point to the aligned allocator with a default alignment (fixed to 16 bytes)
  • Define new macro PyDataAligned_* to align buffer with arbitrary alignment
@numpy-gitbot
Copy link
Author

Attachment added by @cournape on 2007-08-11: aligned_v1.patch

@numpy-gitbot
Copy link
Author

Milestone changed to 1.0.4 Release by @alberts on 2007-08-24

Uh oh!

There was an error while loading. Please reload this page.

@numpy-gitbot
Copy link
Author

@charris wrote on 2008-02-24

David, what is the status of this?

@numpy-gitbot
Copy link
Author

@cournape wrote on 2008-02-25

That's something which needs more thinking and work (in particular, we need a small cpu capability detection if we want to use SSE and co in numpy, and aligned allocators are only useful when used with SSE and co in numpy), and anyway can't be integrated for 1.0.5

@numpy-gitbot
Copy link
Author

Milestone changed to 1.1 by @cournape on 2008-02-25

@numpy-gitbot
Copy link
Author

Milestone changed to Unscheduled by @cournape on 2008-08-13

@mattip
Copy link
Member
mattip commented Jan 13, 2019

Closing in favor of #5312 which has much more information

@mattip mattip closed this as completed Jan 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0