Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-04 Thread Dieter Nützel
Am Dienstag, 1. März 2005 19:46 schrieb Roland Scheidegger: > Dieter Nützel wrote: > >>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). > > > > That was my first thought, t

Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-02 Thread Dieter Nützel
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

Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-02 Thread Roland Scheidegger
Roland Scheidegger wrote: Here's a one-liner fix, which will cause CLIPSPAN hopefully never return a negative n1. Seems to work here. Ian, what do you think? Would it be better to have the optimized read/write functions deal with negative values instead? Ah crap those UNLOCK_HARDWARE changes of c

Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-02 Thread Roland Scheidegger
Dieter NÃtzel wrote: 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). That was my first thought, too (moving the window out to the left...) ;-) This is no problem for the generic

Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-02 Thread Dieter Nützel
Am Dienstag, 1. MÃrz 2005 18:06 schrieb Roland Scheidegger: > Dieter NÃtzel wrote: > > 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 > > > >>Mov

Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-01 Thread Dieter Nützel
Am Dienstag, 1. März 2005 19:46 schrieb Roland Scheidegger: > Dieter Nützel wrote: > >>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). > > > > That was my first thought, t

Re: [r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-03-01 Thread Roland Scheidegger
Dieter NÃtzel wrote: 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 0x406a92b

[r200] 'readpix' sigfault back trace SSE/MMX is culprit

2005-02-16 Thread Dieter Nützel
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_BGRA_REV_MMX () from /usr/X11R6/lib/modules/dri/r200_dri.so (gdb) list 262 263TempImage = (GLubyte *) malloc(ImgWidth * ImgHeight * 4 * sizeof(GLubyte))