Hi Tobias,
OK. Though, I find the ChangeLog entry a bit misleading: There is a
(zero-sized) return array.
I have changed the entry to
* generated/m4/ifunction.m4: Always call internal_malloc_size
even when there is a zero-sized return array
on commit.
Thanks for the review!
Thomas Koenig wrote:
this patch fixes the same kind of problems that PR 49479 addressed,
by applying the same kind of fix to another class of function.
OK for trunk and (after a few days) for 4.6?
OK. Though, I find the ChangeLog entry a bit misleading: There is a
(zero-sized) return array.
Hello world,
this patch fixes the same kind of problems that PR 49479 addressed,
by applying the same kind of fix to another class of function.
I have not bothered to find a test case. Regression-tested.
OK for trunk and (after a few days) for 4.6?
Thomas
2011-09-08 Thomas Koenig
