search for: draw_use_llvm

...ice in the past because radeonsi uses > llvm as well. FWIW the nv30 gallium driver will only use llvm as part of 'draw' when falling back to the swtnl path. This should be extremely rare. But easy enough to build mesa with --disable-gallium-llvm to double-check (or what was the env var? DRAW_USE_LLVM=0 or something along those lines). -ilia

...ll. >> >> >> FWIW the nv30 gallium driver will only use llvm as part of 'draw' when >> falling back to the swtnl path. This should be extremely rare. But >> easy enough to build mesa with --disable-gallium-llvm to double-check >> (or what was the env var? DRAW_USE_LLVM=0 or something along those >> lines). > > > I've tried building with --disable-gallium-llvm, this does not help, > this is not really surprising since on Fedora both libreoffice and > mesa use the system llvm, so there should be no problems with them > expecting differen...

Hi, On 27-08-15 15:46, Marek Olšák wrote: > On Thu, Aug 27, 2015 at 3:09 PM, Hans de Goede <hdegoede at redhat.com> wrote: >> Hi All, >> >> While debugging: https://bugzilla.redhat.com/show_bug.cgi?id=1008089 >> >> I made a apitrace recording of the a single slide transition >> animation, and since I suspected memory corruption replayed >> it

...t;> FWIW the nv30 gallium driver will only use llvm as part of 'draw' when >>>> falling back to the swtnl path. This should be extremely rare. But >>>> easy enough to build mesa with --disable-gallium-llvm to double-check >>>> (or what was the env var? DRAW_USE_LLVM=0 or something along those >>>> lines). >>> >>> >>> >>> I've tried building with --disable-gallium-llvm, this does not help, >>> this is not really surprising since on Fedora both libreoffice and >>> mesa use the system llvm, so...