ok so my stumbling upon this content is really fortuitous because I know very little about programming, but have decided to learn C and MIPS asm for the R3000 the PS1 used so I can learn to decompile Megaman Legends and Serial Experiments Lain for PS1. I don't know if you have any playstation reverse engineering stuff in the pipeline but I would absolutely LOVE that, as this is a bit overwhelming at first!
Are you writing a PS1 emulator to aid with disassembly? If not, I'd advise you to start there, because you could step through the code as it's running. If you don't want to write one yourself, then consider using one of the numerous open source PS1 emulators as a starting point. I would recommend PCSX-ReARMed, as I found its source code rather easy to navigate when I used it on my Raspberry Pi and had to modify it to work with my controller.
Hey 👋 can you create a separate playlist for RISC-V assembly as well, I want to start watching all from the beginning and it would be so much helpful and appreciated, thanks 😊
I'm really curious as to why RISC-V Assembly separates the addresses into "upper" high-order bits (most significant part) versus the low-order bits (the least significant part). Is it related to WORD alignment, I wonder? Also, is this unique to RISC-V or other Assembly languages do it too...?
Because you can't fit 32 bits of immediate into an instruction that itself is 32 bits long. You'd have no space for the actual instruction encoding. The interesting thing is the split at 20 bits, which means if your data section is 4k aligned/sized then really you only need to load the upper bits once and then only need to load the lower whenever you change locations.
Real programmers input raw binary machine code and data, manually on front panel IBM mainframes… and they load the entire OS without a paper printout, just purely from memory.
Only this video preview is the best pointers explanations I have seen before 😂
Just came to say this. This made me believe I have the chance at understanding wtf a pointer is.
Your production is incredible, these are so many lain references
Lol i love the thumbnail
same it's funny as
lmao came here just to say that
int **
Me too 🤣
THANK YOU SO MUCH FOR THE VIDEOOOO, i'm so obsessed with risc-v atm 😭😭😭😭😭
Same! I wanna learn how to make game emulators using it.
Amazing content like always!
You have such a great channel.
clicked on the video and insta-liked because of the preview alone.
thanks for the great content as always, though.
@johnose9326 you mean Anya from IGI's mission director, right!? :D
ok so my stumbling upon this content is really fortuitous because I know very little about programming, but have decided to learn C and MIPS asm for the R3000 the PS1 used so I can learn to decompile Megaman Legends and Serial Experiments Lain for PS1. I don't know if you have any playstation reverse engineering stuff in the pipeline but I would absolutely LOVE that, as this is a bit overwhelming at first!
Are you writing a PS1 emulator to aid with disassembly? If not, I'd advise you to start there, because you could step through the code as it's running. If you don't want to write one yourself, then consider using one of the numerous open source PS1 emulators as a starting point. I would recommend PCSX-ReARMed, as I found its source code rather easy to navigate when I used it on my Raspberry Pi and had to modify it to work with my controller.
Excellent as always👏👏
Thank you, great video !
Interesting the convention for RISC-V.
Hey 👋 can you create a separate playlist for RISC-V assembly as well, I want to start watching all from the beginning and it would be so much helpful and appreciated, thanks 😊
Great explanation!
Adding '#pragma GCC optimize ("O0")' to the beginning of the c-code of the risc-v simulator seems to convince it to not optimize away your example.
16:06 top 2 favorite kinds of dogs! Plus, cowboy bebop is a top 10 anime as well lol
love your videos
Beginning of video is horror but inside lot of knowledge we get
vstspeak my beloved 😂
I like the voice❤
I'm really curious as to why RISC-V Assembly separates the addresses into "upper" high-order bits (most significant part) versus the low-order bits (the least significant part). Is it related to WORD alignment, I wonder?
Also, is this unique to RISC-V or other Assembly languages do it too...?
Because you can't fit 32 bits of immediate into an instruction that itself is 32 bits long. You'd have no space for the actual instruction encoding. The interesting thing is the split at 20 bits, which means if your data section is 4k aligned/sized then really you only need to load the upper bits once and then only need to load the lower whenever you change locations.
This Video is super cool!
Didn't expect you here! Fellow 42 student
I just followed the pointers, like u fellow haha @@cubernetes
Badumtssssss
yeah, nerdy sarcasm is the worst@@cubernetes
i like ur channel. ur funny.
good thumbnail
actual asmr
Interesting they split the load immediate into 20 and 12. Someone was thinking about paging...
wow, what version of windows do you use? It looks like super old version?
seems gentoo
Lol she’s running Linux with a custom bar that just looks like Windows XP I think.
@@psi4j ok cool
im not 32 years old i'm 20 + 12!!!
Thumbnail>>
based anya thumbnail
Wtf am i doing here, I'm just a web developer.
I guess the thumbnail did the job.
Such a cute voice
'int that the way
lui zeros the other bits in the register to 0, I guess.
Normally I can't stand youtubers sticking their dumb faces in dumb expressions on all their dumb thumbnails, but this is accurate
U so cute
no soy face for the thumbnail? it would have been perfect!
Real programmers use Notepad++ 😉
Old programmers use edlin!
Real programmers input raw binary machine code and data, manually on front panel IBM mainframes… and they load the entire OS without a paper printout, just purely from memory.
why do you copy other peoples thumbnails?