8000 Fix 1.9 alignment by charris · Pull Request #5478 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content
8000

Fix 1.9 alignment #5478

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

Merged
merged 2 commits into from
Jan 25, 2015
Merged

Conversation

charris
Copy link
Member
@charris charris commented Jan 22, 2015

Backport of #5316 with potential modification suggested by Julian. After review, extra commit willl be squashed.

If itemsize is a power of two use that as the required alignment up to
the maximum provided by the platform. Power of two sizes may be accessed
via larger moves than bytes.
Non-power of two sizes are accessed bytewise and can thus always be
considered aligned.
Closes numpygh-5293
malloc only provides 8byte alignment and is sufficient to load complex
on x86 platforms.
This fixes the f2py alignment failures with complex types on win32 or on
linux32 with -malign-double
@charris
Copy link
Member Author
charris commented Jan 22, 2015

@juliantaylor Could you check this?

@charris
Copy link
Member Author
charris commented Jan 22, 2015

OK remove 'fixup'.

@juliantaylor
Copy link
Contributor

looks ok, I'll probably backport some more minor stuff this weekend and then we can do a 1.9.2

@juliantaylor
Copy link
Contributor

note I don't know when I'll finish the other fix, I tend to look at the duplication in raw_assign* get anoyed and stop, and I'm also to lazy to actually try to homogenize it ;)

juliantaylor added a commit that referenced this pull request Jan 25, 2015
Fix too large alignment of complex types
@juliantaylor juliantaylor merged commit 1cac77b into numpy:maintenance/1.9.x Jan 25, 2015
@charris charris deleted the fix-1.9-alignment branch February 17, 2015 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0