Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=8218
------- Additional Comments From [EMAIL PROTECTED] 2006-09-19 17:51 -------
(In reply to comment #11)
> Lots of those:
> ==17068== Invalid write of size 4
> ==17068== at 0x4167F6C: emit_vector (r200_maos_arrays.c:287)
> Not sure. I guess it's the float/int casts causing trouble here?
>
> Those in the swtcl path look fairly similar.
> ==17068== Invalid write of size 4
> ==17068== at 0x415F72A: r200_render_quad_strip_verts (t_dd_triemit.h:80)
> IIRC gcc will actually report warnings when compiled with strict aliasing at
> around these places.
That's probably not a related problem, however, I was wrong. Those writes are
invalid because valgrind thinks we're writing past allocated memory. This is
however not the case, again valgrind doesn't know that this memory (those are
writes to the indirect buffers) is allocated elsewhere. Well, that's what I
think happens, at least.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
