@otaria123.bsky.social
Komuniste tomu take pred rokem nerikali cenzura
August 12, 2025 at 5:34 AM
Komuniste tomu take pred rokem nerikali cenzura
Pro takove muze je urcena tvoje cepicka 🤡
August 3, 2025 at 1:54 PM
Pro takove muze je urcena tvoje cepicka 🤡
Komuniste si pred rokem 1989 take mysleli, ze ten komunisticky rezim zachrani pomoci cenzury. Nezachranili
July 30, 2025 at 6:06 AM
Komuniste si pred rokem 1989 take mysleli, ze ten komunisticky rezim zachrani pomoci cenzury. Nezachranili
Takze diskuse bude fungovat jen na profilech populistu a dezolatu? 🤡
July 30, 2025 at 6:05 AM
Takze diskuse bude fungovat jen na profilech populistu a dezolatu? 🤡
Reposted
4/5
When you're debugging, the Chrome Dev Tools will assign a name to that global based on the contents of the string. So, if your string constant is:
"Hello! This is a string…a long one!"
…then a `global.get` of that will show:
When you're debugging, the Chrome Dev Tools will assign a name to that global based on the contents of the string. So, if your string constant is:
"Hello! This is a string…a long one!"
…then a `global.get` of that will show:
May 1, 2025 at 11:39 AM
4/5
When you're debugging, the Chrome Dev Tools will assign a name to that global based on the contents of the string. So, if your string constant is:
"Hello! This is a string…a long one!"
…then a `global.get` of that will show:
When you're debugging, the Chrome Dev Tools will assign a name to that global based on the contents of the string. So, if your string constant is:
"Hello! This is a string…a long one!"
…then a `global.get` of that will show:
Reposted
2/5
The Stage 4 "JS string builtins" feature allows you to import and reference JavaScript string constants.
It's supported in V8/Node via the `--experimental-wasm-imported-strings` flag
You need to import a global of type `externref`, where the import *name* is the string itself:
The Stage 4 "JS string builtins" feature allows you to import and reference JavaScript string constants.
It's supported in V8/Node via the `--experimental-wasm-imported-strings` flag
You need to import a global of type `externref`, where the import *name* is the string itself:
May 1, 2025 at 11:39 AM
2/5
The Stage 4 "JS string builtins" feature allows you to import and reference JavaScript string constants.
It's supported in V8/Node via the `--experimental-wasm-imported-strings` flag
You need to import a global of type `externref`, where the import *name* is the string itself:
The Stage 4 "JS string builtins" feature allows you to import and reference JavaScript string constants.
It's supported in V8/Node via the `--experimental-wasm-imported-strings` flag
You need to import a global of type `externref`, where the import *name* is the string itself:
Reposted
Itanium is kinda a cute ISA, it's a shame it needed a sentient compiler in order to produce any performant code at all :v
But yeah, VLIW ISAs are pretty neat!
But yeah, VLIW ISAs are pretty neat!
April 15, 2025 at 7:21 PM
Itanium is kinda a cute ISA, it's a shame it needed a sentient compiler in order to produce any performant code at all :v
But yeah, VLIW ISAs are pretty neat!
But yeah, VLIW ISAs are pretty neat!
Reposted
i mean honestly making JIT assembly recompilation with a bonkers VLIW architecture 'boring' is an engineering accomplishment in of itself but im talking about like.. more 'native' stuff i guess?
November 25, 2024 at 12:42 AM
i mean honestly making JIT assembly recompilation with a bonkers VLIW architecture 'boring' is an engineering accomplishment in of itself but im talking about like.. more 'native' stuff i guess?
Reposted
PowerPC was an utterly brilliant ISA at the time - it's kinda sad from a nerdy perspective that modern consoles are just x86 boxes with super-duper custom software - there was a time in the 2000s where it felt like wacky CPU ideas were starting to take off (SPEs, VLIW processors like Itanium, etc.)
January 29, 2024 at 11:37 PM
PowerPC was an utterly brilliant ISA at the time - it's kinda sad from a nerdy perspective that modern consoles are just x86 boxes with super-duper custom software - there was a time in the 2000s where it felt like wacky CPU ideas were starting to take off (SPEs, VLIW processors like Itanium, etc.)
Reposted
The Transmeta Crusoe was a 700MHz VLIW processor that “simulated” a ~500MHz x86 Intel chip.
Their virtual machine, known as Code Morphing Software, was flexible enough to emulate other ISAs as well.
Early demos even showed off the Crusoe running Java bytecode!
Their virtual machine, known as Code Morphing Software, was flexible enough to emulate other ISAs as well.
Early demos even showed off the Crusoe running Java bytecode!
April 18, 2025 at 10:28 PM
The Transmeta Crusoe was a 700MHz VLIW processor that “simulated” a ~500MHz x86 Intel chip.
Their virtual machine, known as Code Morphing Software, was flexible enough to emulate other ISAs as well.
Early demos even showed off the Crusoe running Java bytecode!
Their virtual machine, known as Code Morphing Software, was flexible enough to emulate other ISAs as well.
Early demos even showed off the Crusoe running Java bytecode!
Make libtards great again
March 21, 2025 at 7:58 PM
Make libtards great again