On 4/4/25 08:46, Michal Prívozník wrote:
> On 4/3/25 18:28, Roman Bogorodskiy wrote:
>> Michal Prívozník wrote:
>>
>>> On 4/2/25 19:24, Roman Bogorodskiy wrote:
The 'plain' optimization type also triggers the clang stack frame size
issues, so increase limit for it as well.
Sig
Michal Prívozník wrote:
> On 4/2/25 19:24, Roman Bogorodskiy wrote:
> > The 'plain' optimization type also triggers the clang stack frame size
> > issues, so increase limit for it as well.
> >
> > Signed-off-by: Roman Bogorodskiy
> > ---
> > meson.build | 2 +-
> > 1 file changed, 1 insertion
On 4/4/25 11:02, Roman Bogorodskiy wrote:
> Michal Prívozník wrote:
>
>>
>
> IIRC, the first time I've encountered this issue was actually a test
> file. So I guess it would still make sense to keep the workaround for
> clang for now, dropping the optimization condition?
Maybe, but I haven't
Michal Prívozník wrote:
> On 4/4/25 08:46, Michal Prívozník wrote:
> > On 4/3/25 18:28, Roman Bogorodskiy wrote:
> >> Michal Prívozník wrote:
> >>
> >>> On 4/2/25 19:24, Roman Bogorodskiy wrote:
> The 'plain' optimization type also triggers the clang stack frame size
> issues, so inc
On 4/3/25 18:28, Roman Bogorodskiy wrote:
> Michal Prívozník wrote:
>
>> On 4/2/25 19:24, Roman Bogorodskiy wrote:
>>> The 'plain' optimization type also triggers the clang stack frame size
>>> issues, so increase limit for it as well.
>>>
>>> Signed-off-by: Roman Bogorodskiy
>>> ---
>>> meson
On Thu, Apr 03, 2025 at 02:08:28PM +0200, Michal Prívozník via Devel wrote:
> On 4/2/25 19:24, Roman Bogorodskiy wrote:
> > The 'plain' optimization type also triggers the clang stack frame size
> > issues, so increase limit for it as well.
> >
> > Signed-off-by: Roman Bogorodskiy
> > ---
> > me
On 4/2/25 19:24, Roman Bogorodskiy wrote:
> The 'plain' optimization type also triggers the clang stack frame size
> issues, so increase limit for it as well.
>
> Signed-off-by: Roman Bogorodskiy
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.