I don’t think you can guarantee no address space collisions just because you aren’t exceeding 4GB. That would depend on all sorts of starting addresses and load addresses for various uses of memory. If anything in a 64bit build sets the high bits before heap growth then the lower 32 bits might very well overlap with the assumption that it’s safe. The only thing that would save you is luck and running a small program, and by small I don’t mean
@@Diamonddrake the reason for lopping off the high bits is to remap large addresses to small. This is not about being too big, it’s about zeroing of the MSBs leading to overlapping address spaces in the remaining 32 bits. The point of 64bit is to give lots of virtual address space headroom between heap, stack, loaded binaries other data and even device mapped memory. Nothing in that mess guarantees that the 32bit LSB of any of the above won’t overlap and cause nasty unpredictable bugs. I did a quick Google search and there are some flags that seemed relevant but that was a different dev environment entirely.
@@Diamonddrake P.S. running with your idea differing MSB with matching LSB could be detected but that seems like it would take additional storage and be dog slow. Some kind of page map of 32 bit addressable memory reserved with the first truncated MSB to access. So at least you'd detect disaster if a subsequent read or write used a different MSB. But this is really not a healthy scenario.
@@TsodingDaily 😳 Point taken. I'm not clear on what populates the virgin address space of an executing WASM context and was talking in generalities but with some significant gaps in my knowledge.
Really cool approach to fixing the issue, hope I get the opportunity to try Jai before too long. You tend to pronounce 'b' as 'ы', and you sound really unique due to it.
I'm glad to see there's some overlap between serenity and tsoding communities. But uh, if his Zig stream is any indication, it's probably best not to bug him to use the language unless you have a couple hundred bucks and some way to send that money to Russia :^)
If gay propaganda is forbidden in Russia how are you able to openly code in c++?
Ещё больше вопросов вызывает, что на жс он тоже пишет.
Yes, coding and c++ is so gay c# is so much better
@@skeleton_craftGaming High level noobs
@@EyeNeo bro low level devs dont make a cent, its donations, and they only do it because they want to
Finally Tsoding is back after 10 days 🔥🔥🔥
Have you ever been to Twitch?
Mr Tsoding, your code is just on another level. Great concepts, a lot to learn! We do appreciate your work. Congrats from Bulgaria
One hour intro and some copy-paste. The true c++ experience
@46:51 for comparing text files, you could use "git diff file1.txt file2.txt" :)
It doesn't need a git directory to work.
Doesn't git just call out to whatever your default diff tool is anyway? If that's the case, you might as well just run it directly.
@@Bobbias Not for me on Windows with "git diff". There might be a command to show it though. (or I can't find it in the default help page of git diff)
I’m not a wasm programmer nor a C++ one but I really enjoyed and learned many things from this watch ❤️
How about that!
Keep up the nice videos. I enjoy watching them.
My man literally named it Leaked IP.
OMG... Why is "src/..." prefix in `#include "src/*.h"` headers? omg... really great build system xD 01:15:12
Always waiting ur vids. Love u
I don’t think you can guarantee no address space collisions just because you aren’t exceeding 4GB. That would depend on all sorts of starting addresses and load addresses for various uses of memory. If anything in a 64bit build sets the high bits before heap growth then the lower 32 bits might very well overlap with the assumption that it’s safe. The only thing that would save you is luck and running a small program, and by small I don’t mean
It’s not guaranteed but the added functions could guard and assert if a pointer was too big showing how likely the issue is with a memory stress test
@@Diamonddrake the reason for lopping off the high bits is to remap large addresses to small. This is not about being too big, it’s about zeroing of the MSBs leading to overlapping address spaces in the remaining 32 bits. The point of 64bit is to give lots of virtual address space headroom between heap, stack, loaded binaries other data and even device mapped memory. Nothing in that mess guarantees that the 32bit LSB of any of the above won’t overlap and cause nasty unpredictable bugs. I did a quick Google search and there are some flags that seemed relevant but that was a different dev environment entirely.
@@dorbie Where is the loaded binary located within the WebAssembly Memory?
@@Diamonddrake P.S. running with your idea differing MSB with matching LSB could be detected but that seems like it would take additional storage and be dog slow. Some kind of page map of 32 bit addressable memory reserved with the first truncated MSB to access. So at least you'd detect disaster if a subsequent read or write used a different MSB. But this is really not a healthy scenario.
@@TsodingDaily 😳 Point taken. I'm not clear on what populates the virgin address space of an executing WASM context and was talking in generalities but with some significant gaps in my knowledge.
Really cool approach to fixing the issue, hope I get the opportunity to try Jai before too long. You tend to pronounce 'b' as 'ы', and you sound really unique due to it.
ewwwwwww c++
When tsoding has a 1 hour into, you know it's gonna be good.
Great programming as always :) Very cool tool!
Discord link please?
He was having PTSD from OOP madness in C++. haha!
I've seen the term intrusive used before but never bothered to look up what it was. Well now I know. I'm not sure if I wanted to know this or not...
where can i join your discord?
Is there any wasm32234?
the domain is down :(
ty bro, keep going!
amazing
You could create an AI that modifies itself in Jai
Автор из России?
Да, акцентик слышен)))
hack on Jakt (from the Serenity people)
I'm glad to see there's some overlap between serenity and tsoding communities. But uh, if his Zig stream is any indication, it's probably best not to bug him to use the language unless you have a couple hundred bucks and some way to send that money to Russia :^)