On Thu, Jun 13, 2019 at 03:59:33PM +0000, Michael Matz wrote:
> without running the risk of unlimited stack use. But of course this would
> promote a programming style that'd only work with our alloca (and not even
> C-alloca), and we want to avoid that. I thought it a cute idea, but was
> carried away by the cuteness ;-)
>
> I like the suggestion of setting (and carrying through the pipeline) the
> TREE_NO_WARNING flag on an source 'alloca(0)'.
Ditto, though it would be nice one day to implement
TREE_NO_WARNING/gimple_no_warning_p as a bit indicating on the side
sets of disabled warnings rather than the current big hammer where
that bit disables all warnings.
Jakub
