On Sat, Oct 8, 2016 at 9:30 AM, Marek Olšák <mar...@gmail.com> wrote:
> On Sat, Oct 8, 2016 at 5:58 PM, Jason Ekstrand <ja...@jlekstrand.net> > wrote: > > FYI, we use ralloc for a lot more than just the glsl compiler so the > first > > few changes make me a bit nervous. There was someone working on making > our > > driver more I undefined-memory-friendly but I don't know what happened to > > those patches. > > shader-db + valgrind can be used to track down uninitialized variables. > > After that's done, test suites (piglit etc.) can be used to fix any > remaining uninitialized variables (run test suites first and then run > regressed tests with valgrind). > > That's how I did it for GLSL. > Yeah, that's more-or-less how I would do it. I just didn't want you pushing anything without us fixing things. :) > Alternatively, the following can be done: All non-GLSL code can be > switched from ralloc to rzalloc. All non-GLSL C++ classes can be > switched from DECLARE_RALLOC_CXX_OPERATORS to > DECLARE_RZALLOC_CXX_OPERATORS. > > Marek >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
