Chris Tate 98cc35de09 Find the code segment that holds the runtime under musl too ...

The constructor took the program object with an empty name for the main
program, which is how glibc reports it. musl reports the main program
with its path, or "/proc/self/exe" in a static executable, so on musl
targets --large-pages found no segment and left the code file-mapped.
The constructor now takes the executable segment that holds its own code:
the runtime links into the executable, so that is the main program's
code under either C library.

scr_text_pages.test.ts runs its check against a static musl build made
with zig as well as the glibc build.

2026-10-26 23:55:27 -05:00

..

src

Find the code segment that holds the runtime under musl too

2026-10-26 23:55:27 -05:00

test

Allocate template literals at their exact length

2026-10-26 21:01:36 -05:00

vendor

Build node:zlib on the zlib Node bundles

2026-10-26 15:12:51 -05:00

LICENSE

init

2026-07-22 18:08:04 -05:00

package.json

Prepare v0.4.5 release

2026-10-25 11:26:13 -05:00