Skip to content
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.

Sign up for GitHub

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

Jump to bottom

VFP version doesnt work with sign=1 #2

Closed
matszpk opened this issue Apr 21, 2013 · 2 comments
Closed

VFP version doesnt work with sign=1 #2

matszpk opened this issue Apr 21, 2013 · 2 comments

Comments

@matszpk
Copy link
Contributor

matszpk commented Apr 21, 2013

Firstly, I appreciate your efforts to create this amazing library. Unfortunatelly support for VFP was not finished. Do you can fix support for VFP by adding support for sign=1? Computations for sign=1 are wrong (generates wrong results). I will be very glad, when this bug would be fixed quickly.
Edit: Sorry. Bug concerns sign=1 (not -1). Simply I forgot :(
@anthonix
Copy link
Owner

Hi, I've finished the VFP code (well, 1D complex -- there is still some NEON code in the real and ND VFP transforms).

Please try the code, and send me a postcard if you like FFTS =)

@matszpk
Copy link
Contributor Author

matszpk commented Apr 24, 2013

Thank you. I confirm. current version of a library works fine.

linkotec referenced this issue in linkotec/ffts Nov 30, 2015
@linkotec
Try to fix Travis testing #2
9320b4a
anthonix pushed a commit that referenced this issue Jun 17, 2017
@linkotec
Merge pull request #2 from madscientist159/master
ba0ad24 
Fix various build issues and disable AltiVec support pending adaption for changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matszpk @anthonix