Skip to content

Conversation

@barracuda156
Copy link
Contributor

See: #29758

Copy link
Member

@seberg seberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks. ptrdiff_t vs. npy_intp usage differs a bit between functions now, but it doesn't matter.

EDIT: To be clear, the test failures are unrelated, there are some general problems that will be fixed very soon hopefully (maybe it already is).

Unfortunately, tests are failing. It would be nice if you can move the npts_in just to keep things slightly simpler.

#ifndef POCKETFFT_NO_VECTORS
size_t npts_in = nout / 2 + 1;

#endif
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nicer to just move it into the existing #ifndef below, but a small nit, but thanks for fixing the warning!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, while you are at it, please do move it inside (it should have been there in the first place, as it is not used outside).

@barracuda156
Copy link
Contributor Author

@seberg Do we need to change something here at the moment re test failures?

@seberg
Copy link
Member

seberg commented Sep 20, 2025

It would be nice to move that one thing, but otherwise should be all good. We can re-trigger CI manually (or close/reopen PR) when things are resolved.

Copy link
Contributor

@mhvk mhvk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching this -- as @seberg noted in the issue, the reason I used ptrdiff_t here was that that was what pocketfft expected. I vaguely recall getting compiler warnings without it, but if this works now without explicit casts, then all fine by me.

#ifndef POCKETFFT_NO_VECTORS
size_t npts_in = nout / 2 + 1;

#endif
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, while you are at it, please do move it inside (it should have been there in the first place, as it is not used outside).

Copy link
Member

@mattip mattip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM pending CI success

@seberg seberg merged commit 19f2a72 into numpy:main Sep 22, 2025
79 of 80 checks passed
@seberg seberg changed the title _pocketfft_umath.cpp: fix types BUG: Fix pocketfft umath strides for AIX compatibility Sep 22, 2025
@seberg seberg changed the title BUG: Fix pocketfft umath strides for AIX compatibility BUG: Fix pocketfft umath strides for powerpc compatibility Sep 22, 2025
@barracuda156
Copy link
Contributor Author

@seberg Thank you for helping here, and sorry for a delay, I did not have much time this weekend.

@barracuda156 barracuda156 deleted the pocketfft branch September 22, 2025 08:58
@seberg seberg added the 09 - Backport-Candidate PRs tagged should be backported label Sep 22, 2025
charris pushed a commit to charris/numpy that referenced this pull request Sep 23, 2025
* _pocketfft_umath.cpp: fix types

Fixes: numpy#29758
Credits to @seberg

* _pocketfft_umath.cpp: fix unused variable warning

* Move npts_in calculation into #ifndef

---------

Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
@charris charris removed the 09 - Backport-Candidate PRs tagged should be backported label Sep 23, 2025
charris added a commit that referenced this pull request Sep 23, 2025
BUG: Fix pocketfft umath strides for AIX compatibility (#29768)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants