On 31 October 2016 at 20:47, Jason Ekstrand <[email protected]> wrote: > On Mon, Oct 31, 2016 at 8:34 AM, Emil Velikov <[email protected]> > wrote: >> >> On 31 October 2016 at 15:11, Ilia Mirkin <[email protected]> wrote: >> > Hi Emil, >> > >> > It appears that you missed cherry-picking one of Samuel's commits: >> > >> > commit 84e946380b2d5ddc62a107b667be39abf1932704 >> > Author: Samuel Pitoiset <[email protected]> >> > Date: Wed Oct 26 23:10:53 2016 +0200 >> > >> > nvc0/ir: fix emission of IMAD with NEG modifiers >> > >> > The emitter tried to emit sub instead of subr when src0 has >> > actually a NEG modifier. >> > >> > Signed-off-by: Samuel Pitoiset <[email protected]> >> > Reviewed-by: Ilia Mirkin <[email protected]> >> > Cc: "11.0 12.0 13.0" <[email protected]> >> > >> > Perhaps you can have a look at why that happened and look for any >> > other commits you might have missed? >> > >> Yes, this and another two Intel commits landed as the branch was going >> through piglit/deqp/cts testing. > > > What two Intel patches? 4964a5149b7776ce27aaeab2be0c2ebf41ded740 intel/blorp: Fix a couple asserts around image copy rectangles
43dadb6edd5e3e3e10b1198184a9f75556edad49 intel/blorp: Rework our usage of ralloc when compiling shaders These two at time of writing - mem leak + assert fix. > There is a fixed GPU hang that should be CC'd 2a4a86862c949055c71637429f6d5f2e725d07d8 i965/fs/generator: Don't use the address immediate for MOV_INDIRECT This one I believe ? > stable. Also, by "scoop them up" do you mean that they will be in 13.0? > Yes, that's correct. Thanks Emil _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
