From octave-maintainers-request at bevo dot che dot wisc dot edu Tue Feb 17 20:26:25 2004
Subject: Re: potential problem with fftw changes
From: Paul Kienzle <pkienzle at users dot sourceforge dot net>
To: octave-maintainers mailing list <octave-maintainers at bevo dot che dot wisc dot edu>
Date: Tue, 17 Feb 2004 21:25:32 -0500


On Feb 17, 2004, at 1:19 PM, John W. Eaton wrote:

> On 17-Feb-2004, David Bateman <David dot Bateman at motorola dot com> wrote:
>
> | Given that we can't get the correct data alignment, we do need to 
> check the
> | alignment for the plans. So we need the cast to int or long? Is
> |
> |    char in_align = in & 0xF;
> |    char out_align = out & 0xF;
> |
> | alright? Will it be correct for all platforms?
>
> G++ won't compile that if in and out are pointers to double.  So I
> changed it to
>
>   char in_align = (reinterpret_cast<long> (in)) & 0xF;
>
> which I think will work provided that pointers and long are the same
> size.

Are you sure you don't want ptrdiff_t from <cstddef> rather
than int or long?

Paul Kienzle
pkienzle at users dot sf dot net