WASM Internals Part 1

#1

Post by A_N_T_O_N_I_O » Wed, Dec 22, 2021, 6:36 PM UTC

Re: WASM Internals Part 1

#2

Post by A_N_T_O_N_I_O » Wed, Dec 22, 2021, 6:36 PM UTC

Hi everyone!!, today I'm quite excited because I have never posted anything on Hacker News and I have always wanted to give back a little piece of my own apportation to a huge and valuable community as you all are to me.

I hope you like it and I will try to keep improving my writing capabilities and touch on interesting topics.

Re: WASM Internals Part 1

#3

Post by ffhhj » Wed, Dec 22, 2021, 10:02 PM UTC

Nice! Will look for your future tutorials. I was able to create a little js->wasm obfuscation tool with emscripten, but for some reason when I tried to initialize a C array larger than 512 bytes I always get errors. My work around was defining the array of given size and storing the obfuscated binary byte per byte. Wasm files seem to be 4x larger this way. Maybe this time I'll make it directly in webassembly.

Re: WASM Internals Part 1

#4

Post by lioeters » Wed, Dec 22, 2021, 10:03 PM UTC

Thank you for writing the article, it's good introductory material on the topic.

Found a typo: "moudle" -> "module"

https://github.com/antferdom/wasm_playground/blob/f380f675da...

Re: WASM Internals Part 1

#5

Post by A_N_T_O_N_I_O » Wed, Dec 22, 2021, 10:37 PM UTC

lioeters wrote: post #4

Thank you for writing the article, it's good introductory material on the topic. Found a typo: "moudle" -> "module" https://github.com/antferdom/wasm_playground/blob/f380f675da...

Many thanks for your kind and valuable reply to my first post. I will definitely after having seen the replies keep it up with the series around one post per week!. I want to emphasize the detail and formalism of the content.

AND I have already modified the misspelling. Thank you as well for that one, as it also means that you read it haha.

Re: WASM Internals Part 1

#6

Post by A_N_T_O_N_I_O » Wed, Dec 22, 2021, 10:41 PM UTC

ffhhj wrote: post #3

Nice! Will look for your future tutorials. I was able to create a little js->wasm obfuscation tool with emscripten, but for some reason when I tried to initialize a C array larger than 512 bytes I always get errors. My work around was defining the array of given size and storing the obfuscated binary byte per byte. Wasm files seem to be 4x larger this way. Maybe this time I'll make it directly in webassembly.

I'm so grateful for your interest in the upcoming chapters!!. I would love to take a look at your issue related to the array compilation to wasm. Anyways I encourage you to try to directly write it on .wat and compare the results for researching. I will definitely love to see more about this.