mirror of https://git.musl-libc.org/git/musl
Browse Source
traditionally, we've provided a guarantee that dynamic-linked applications with no external dependencies (nothing but libc) and no thread-local storage have no failure paths before the entry point. normally, thanks to reclaim_gaps, such a malloc will not require a syscall anyway, but if segment alignment is unlucky, it might. use a builtin array for this common special case.master
1 changed files with 10 additions and 3 deletions
Loading…
Reference in new issue