[Insight-developers] Empty FixedArray destructor: Performancehit using gcc (times 2)

[Sean McBride]

On 6/5/08 11:40 PM, Tom Vercauteren said:

>Just to try and make things clearer. The current memory alignment is
>not actually wrong. The computation results are indeed correct.
>However the pointer is simply not aligned on 8 bytes which is thus not
>optimal in terms of performance. When I said "bad alignment", I
>actually meant "alignment leading to slow memory accesses".

I'm afraid I haven't followed this thread very closely, but... this
memory that is not aligned as you'd like, how was it allocated? 
malloc()?  new?  Or is it an instance variable in a class/struct?

-- 
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada