Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-10-10 Thread Frank Mori Hess
On Friday 09 October 2009, Matteo Frigo wrote: > Your bug report implies that calling fftw from a program that > #include's causes a violation of the aliasing rules, > because fftw is compiled with fftw_complex = double [2] and the > program is compiled with fftw_complex = double _Complex. I cont

Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-10-09 Thread Matteo Frigo
Yes, I understand that you can write a program that breaks the aliasing rules. However, this is not what this bug report is about. Your bug report implies that calling fftw from a program that #include's causes a violation of the aliasing rules, because fftw is compiled with fftw_complex = doubl

Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-10-05 Thread Frank Mori Hess
On Monday 28 September 2009, Frank Mori Hess wrote: > The > strict aliasing rules allow compilers to make optimizations that assume > pointers to different types will not access the same memory. I'll try > to produce a test program soon. Attached is an example program that shows undefined behavio

Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-09-28 Thread Frank Mori Hess
On Monday 28 September 2009, Matteo Frigo wrote: > > Frank Hess wrote: > > > This means if a user doesn't include fftw3.h first, before any > > > possible inclusion of complex.h, then his code may be using a > > > different ABI than that of the libfftw3.so provided by debian. > > This is false. [N

Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-09-28 Thread Matteo Frigo
> Frank Hess wrote: > > > This means if a user doesn't include fftw3.h first, before any > > possible inclusion of complex.h, then his code may be using a > > different ABI than that of the libfftw3.so provided by debian. This is false. [N843, 6.2.5 Types, verse 13]: Each complex type has th

Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-09-28 Thread Paul Brossier
severity 534722 normal forwarded 534722 f...@fftw.org thanks Hello Frank, The upstream authors are included in this thread. Frank Hess wrote: > Package: libfftw3-dev > Version: 3.1.2-3.1 > Severity: important > > FFTW3 has a mis-design feature where if complex.h is included before fftw3.h > (m

Bug#534722: libfftw3-dev: aliasing violations due to complex.h inclusion

2009-06-26 Thread Frank Hess
Package: libfftw3-dev Version: 3.1.2-3.1 Severity: important FFTW3 has a mis-design feature where if complex.h is included before fftw3.h (maybe indirectly and unintentionally through another header) then the header changes the definition of the "fftw_complex" types (without doing any mangling t