Hello world, the memory allocation for the buffer in the library matmul routines still has one problem: The value of 0xdeadbeef meant as poison could end up in the calculation of the size of the buffer for the blocked matmul.
The attached patch fixes that. Verified with regression-test, also by running a few select test cases under valgrind. No test case because nothing appeared to fail. OK for trunk? Regards Thomas 2017-05-10 Thomas Koenig <tkoe...@gcc.gnu.org> * m4/matmul_internal.m4: Set bystride to correct value for later calculation of buffer size. * generated/matmul_c10.c: Regenerated. * generated/matmul_c16.c: Regenerated. * generated/matmul_c4.c: Regenerated. * generated/matmul_c8.c: Regenerated. * generated/matmul_i1.c: Regenerated. * generated/matmul_i16.c: Regenerated. * generated/matmul_i2.c: Regenerated. * generated/matmul_i4.c: Regenerated. * generated/matmul_i8.c: Regenerated. * generated/matmul_r10.c: Regenerated. * generated/matmul_r16.c: Regenerated. * generated/matmul_r4.c: Regenerated. * generated/matmul_r8.c: Regenerated.