[patch, fortran] PR 80687, 80696

[Thomas Koenig]

Hello world,

it appears that using VLAs also caused the strange errors reported
in PR 80696.  This, together with Janne's comment, has made me decide
that maybe using malloc/free is not such a bad idea after all.

So, here is the updated patch.  Running regression-testing with -m32
at the moment.  OK for trunk if it passes?

Regards

	Thomas

2017-05-09  Thomas Koenig  <tkoenig@gcc.gnu.org>

         PR fortran/80687
         PR fortran/80696
         * m4/matmul_internal.m4:  'matmul_name`:  Always
         use malloc/free to allocate t1.
         * 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p3.diff
Type: text/x-patch
Size: 58458 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20170509/c8d314f0/attachment.bin>