On Wed, Dec 21, 2016 at 12:05 PM, Andre Vehreschild <ve...@gmx.de> wrote: > Hi all, > > so I have learned that proposing to write "speaking code" is not very well > taken.
If you want to make a patch introducing gfc_size_t_zero_node, go ahead, at least I won't object. I don't think build_zero_cst(size_type_node) is that terrible myself, but I don't have any hard opinions on this. > Anyway, there is a patch (in two parts) hanging about changing the character > length from int to size_t. It looks ok to me, but I do not have the privilege > to ok it. Furthermore am I still not convinced that we can't do anything about > the failing testcase allocate_deferred_char_scalar_1. So how do we proceed? I have just verified that my fix for PR 78867 fixes the -flto failures Dominique noticed. I have some other minor cleanup to do to the charlen->size_t patch, and then I'll resubmit it. But yes, I'm still seeing the warning messages with -O1 for allocate_deferred_char_scalar_1.f03. AFAICT it's a bogus warning, but I don't know how to get rid of it.. -- Janne Blomqvist