Hey, I know that trunk is a moving target, but it's now something like two months that the trunk is not working for me.
I was wondering if big stuff is still in flux or i'm the victim of several subtle x86_64 bugs that lead to complete non working workflow :-) This stuff seems not to work at all: - temperature/tint - lens correction Stuff that seems to work, but not completly: - batch processing, sometimes i can't get stuff added in there or i can"t start the process using the button on the batch tab Is it all expected because under work ? Tell me if you need more x86_64 bug testing. Also, i have a more general question, why did you switch to intrinsics ? Certain (well almost all versions) of gcc are known to produce horrible code using intrisics.I remember from personal experience that in lot of cases intrinsics led to very poor mmx/sse code that used lot of load/store storms from/to stack. Moreover this was non op code like: movq [esp], mm0 movq mm0, [esp] At that time, gcc devs explained that this was caused by some sort of aliasing problem that gcc can't solve all by itself. Writing to memory was necessary because gcc can't determine if other pointers could alias the region. But i don't see wide usage of restrict keyword in rawtstudio sources. Do you have a very specific "good" version of gcc you advise ? What speedup/slowdown did you get using the intrinsics instead of inline asm ? Is that motivated by the ease of maintenance (i mean you write code once and this uses more registers on x86_64 than on ia32 ?) Just curious about this intrinsics move :-) -- Edouard Gomez _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
