An r300g user seems to hit this issue when st/mesa uses Draw for feedback mode, in Compiz. There is the backtrace attached in the bug report below. The reporter doesn't use LLVM too and he bisected the same bad commit as you (gallium: implement bounds checking for constant buffers).
https://bugs.freedesktop.org/show_bug.cgi?id=29311 Best regards. -Marek On Fri, Jul 30, 2010 at 11:52 PM, Jerome Glisse <gli...@freedesktop.org>wrote: > On 07/30/2010 05:02 PM, Jakob Bornecrantz wrote: > >> On 30 jul 2010, at 13.32, Brian Paul wrote: >> >>> On 07/30/2010 12:38 PM, Jerome Glisse wrote: >>> >>>> Hi Brian, >>>> >>>> I am facing a strange segfault with r600g on top of lastest git, >>>> git bisect pointed to gallium: implement bounds checking for constant >>>> buffers >>>> My feeling is that it should only affect software pipeline but >>>> somehow r600g seem to take different path now, attached if full >>>> but i can't make much sense out of it, do you have a clue on what >>>> might went wrong ? >>>> >>> >>> I took a quick look but didn't find anything. >>> >>> Maybe try a make clean and rebuild just in case? >>> >> >> I'm getting the same with swrastg on in 32bit VM, "git clean -fdx":ed >> even. >> >> Cheers Jakob. >> > > Brian, it only affects SSE path, i thought change to struct > tgsi_exec_machine > was causing some of the generated code to access wrong data but it doesn't > seems to be that (moved ConstsSize to bottom of struct def without effect). > > Jerome > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
