[Insight-developers] Empty FixedArray destructor: Performance hit using gcc (times 2) : __attribute__ ((aligned (8)))

[Luis Ibanez]

Hi Tom,


I have no objection to removing the empty destructor of the FixedArray.


However, removing that code without understanding "why" is that it makes
a difference for the alignment, seems to be a dangerous way to maintain
the toolkit.


We are also badly place at this point to judge on how much this issue
matters for other platforms.


We will know more about it tomorrow morning when we see the outcome of
itkFixedArrayTest2 in the Dashboard.


In either case, we must document this observations in the code,
to make sure that the effect of the destructor presence (or absence)
is not forgotten.



     Luis


------------------------
Tom Vercauteren wrote:
> 
> Well I would really vote for removing the empty destructor
> implementation. This seems to be the cleanest way to solve the
> problem. The empty destructor is useless and only interferes here. I
> don't really like changing compilation flags or adding macros and
> adding a new derived class would be confusing for the user.
> 
> Tom
>