On Fri, Dec 30, 2022 at 2:51 PM Jakob Reschke <jakres+squeak@gmail.com> wrote:
 
That's why (quoted from the doc page):

Unlike _alloca, which doesn't require or permit a call to free to free the memory so allocated, _malloca requires the use of _freea to free memory.

Still not a good enough justification, IMO.  They could modify the compiler to plant a call to _freea on return.  I'm also curious to see if _freea actually does anything.  The whole point of alloca is that deallocation is automatic on return because the memory is stack allocated.

Am Fr., 30. Dez. 2022 um 23:07 Uhr schrieb Eliot Miranda <eliot.miranda@gmail.com>:
 


On Mon, Dec 19, 2022 at 9:29 AM Ron Teitelbaum <ron@usmedrec.com> wrote:
 
Just saw this:
https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/alloca?view=msvc-170

_alloca

Article
10/26/2022

Allocates memory on the stack. This function is deprecated because a more secure version is available; see:


Mucroshaft are such irritating *FUCKS*.  It has exactly the same signature as alloca.  Why didn't they just upgrade the implementation instead of forcing everyone to rewrite their code??



Requirements

RoutineRequired header
_malloca<malloc.h>

All the best,

Ron Teitelbaum


On Mon, Dec 19, 2022 at 12:00 PM Marcel Taeumel <marcel.taeumel@hpi.de> wrote:
 
Hi all!

Has anybody tried to build OSVM in Windows 11 via Cygwin64?

clang-8 does not work because "_alloca" cannot be found ... hmm...


So, who implements _alloca? It's not msvcrt.dll ... how to find that out?

Best,
Marcel


--
_,,,^..^,,,_
best, Eliot


--
_,,,^..^,,,_
best, Eliot