M
ладно, это уже немного оффтоп все.
Size: a a a
2019 November 19
lp
да мб, но тем не менее если кто найдет стальное опровержение или хорошее обьяснение, напишите. Можете в личку
M
проблема в том что libm у musl и libc очень похожи особенно в части тригонометрии со времен Sun там очень мало что поменялось, так что все это действительно "вилами по воде"
M
Я даже знаю про что идет речь. Плишкин работал над flow9
M
MaxGraey
Я даже знаю про что идет речь. Плишкин работал над flow9
ҪҸ
что это вообще такое?
M
Какой то мультикомбайн на подобии haxe
M
"This pass strips DWARF debug sections, but not other debug
sections. This is useful when emitting source maps, as we do
need the SourceMapURL section, but the DWARF sections are
not longer necessary (and we've seen a testcase where they
are massively large, so big the wasm can't even be loaded in
a browser...)."
https://github.com/WebAssembly/binaryen/pull/2454#issue-342845786
Да DWARF секция может быть реально необъетной.
sections. This is useful when emitting source maps, as we do
need the SourceMapURL section, but the DWARF sections are
not longer necessary (and we've seen a testcase where they
are massively large, so big the wasm can't even be loaded in
a browser...)."
https://github.com/WebAssembly/binaryen/pull/2454#issue-342845786
Да DWARF секция может быть реально необъетной.
M
Ага, этот пасс очень неплохо так помогает сократить избыточный подсчет ссылок. И это только начало)
2019 November 20
M
M
MaxGraey
Там про WebAssembly в том числе
M
WebAssembly
Support for multiple code spaces
So far, each WebAssembly module consisted of exactly one code space on 64-bit architectures, which was reserved on module creation. This allowed us to use near calls within a module, but limited us to 128 MB of code space on arm64, and required to reserved 1 GB upfront on x64.
In v7.9, V8 got support for multiple code spaces on 64-bit architectures. This allows us to only reserve the estimated needed code space, and add more code spaces later if needed. Far jump will be used for calls between code spaces that are too far apart for near jumps. Instead of ~1000 WebAssembly modules per process V8 now support several million, only limited by the actual amount of memory available.
Источник: https://v8.dev/blog/v8-release-79
Support for multiple code spaces
So far, each WebAssembly module consisted of exactly one code space on 64-bit architectures, which was reserved on module creation. This allowed us to use near calls within a module, but limited us to 128 MB of code space on arm64, and required to reserved 1 GB upfront on x64.
In v7.9, V8 got support for multiple code spaces on 64-bit architectures. This allows us to only reserve the estimated needed code space, and add more code spaces later if needed. Far jump will be used for calls between code spaces that are too far apart for near jumps. Instead of ~1000 WebAssembly modules per process V8 now support several million, only limited by the actual amount of memory available.
Источник: https://v8.dev/blog/v8-release-79
C
ҪҸ