Closed slouken closed 2 years ago
Sorry for the delay on getting to this. I was intending on actioning this and then forgot about it. Merged into dev and will be released shortly.
Would you be interested in a patch to reduce stack usage? Right now there are several functions which use more than 4K of stack, which generates __chkstk() calls on Visual Studio. The fix would be to dynamically allocate the large objects that are currently declared as stack variables.
That's something I'm definitely not interested in sorry.
That’s what I figured, thanks!
The compiler was warning about prediction128 being used uninitialized.