Someone found a bug in the implementation of FFT when FFTW is activated:
Looking at the implementation, a `fftw_plan` object is created for a real->complex FFT and then reused for a complex->complex FFT.
A possible fix would be to encode whether the src is real or complex as well, when getting the plan object.
-- GitLab Migration Automatic Message --
This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1537.