On Thu, Oct 19, 2017 at 12:28 PM, Eric Botcazou wrote:
>> Looks ok. I wonder if you want to explicitely document that max_size < size
>> doesn't have any effect on actual code generation and is not checked for.
>
> Documentation amended to that effect:
>
> -- Built-in
> Looks ok. I wonder if you want to explicitely document that max_size < size
> doesn't have any effect on actual code generation and is not checked for.
Documentation amended to that effect:
-- Built-in Function: void *__builtin_alloca_with_align_and_max
(size_t size, size_t
On Mon, Oct 16, 2017 at 10:35 AM, Eric Botcazou wrote:
> Hi,
>
> a big limitation of -Wstack-usage/-Wvla-larger-than/-Walloca-larger-than is
> that you need -O2 (or more precisely -ftree-vrp) in order to be able to say
> something sensible for dynamically-sized
Hi,
a big limitation of -Wstack-usage/-Wvla-larger-than/-Walloca-larger-than is
that you need -O2 (or more precisely -ftree-vrp) in order to be able to say
something sensible for dynamically-sized objects/VLAs/calls to alloca. That
can be problematic, for example if the coding guidelines