Am Mittwoch, 16. Februar 2005 21:27 schrieb Dieter NÃtzel:
Any change that someone look into this?
Ian, it seems that's related to your new SSE/MMX code.
Thanks, Dieter
Move window 'out' to the left.
NO sigfault with MESA_NO_SSE and MESA_NO_MMX.
With MMX: #0 0x406a92b5 in _generic_read_RGBA_span_BGRA8888_REV_MMX () from /usr/X11R6/lib/modules/dri/r200_dri.so #1 0x405655af in r200ReadRGBASpan_ARGB8888_MMX (ctx=0x7fffb862, n=194, x=5, y=229, rgba=0x45024008) at spantmp2.h:415
Looking a bit at this, this seems to be caused because the number of pixels to read can be less than zero after CLIPSPAN (don't know if that's a bug in itself or not).
This is no problem for the generic read (since the for loop will just terminate instantly), but the mmx/sse/sse2 optimized routines only test if it's 0 pixels to read, and don't bail out if it's less than zero. I haven't looked closely what exactly will happen (i.e. the loops may never terminate at all), but this certainly seems like a bad thing...
Roland
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
