> Great, I guess submit a patch in the STR form (Software Trouble Report):
>
>       http://fltk.org/str.php
>
> Just click on 'Submit Bug' and fill out the form, outlining the exact
> cpu/graphics combo you're using, in case someone else hits this.
>
> Maybe we can somehow detect this in the configure script, and have an
> #ifdef for it so that it's automatic.

I think, Michael should do deep test of the feature with other images.

Remark: I've created couple of macroses and I use them in these critical places.

pixel = *mem => pixel = LOAD_U32_VO(mem)
*dst = *src  => STORE_U32_VO(dst, *src)

These macroses are defined in case of _normal_ bytes as

#define LOAD_U32_VO(addr )        *((u32*)(addr))
#define STORE_U32_VO(addr, val)   *((u32*)(addr)) = (val)

and in case twisted bytes they will be replaced by  followed functions

#define LOAD_U32_VO(addr )        load_le32( (u32*)(addr) )
#define STORE_U32_VO(addr, val)   store_le32( (u32*)addr, (val) )

When I perform optimized compiling of the library the function turns into one 
PowerPC's command lwbrx or stwbrx.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to