gcn_x86

@[email protected]
84 Followers
181 Following
1,034 Posts

Hi!

I'm interested in gamedev, operating systems, embedded systems, console emulators, electronics and graphics programming. I'm not particularly proficient in any of those, but hey, I'm learning.

I don't post regularly because I tend to work on stuff slowly. Sometimes I do post a lot, though.

...aaaaaaaaaaaaaaaaaaaaaaa
aaaaaAAAAAAAAAAAAAAAAAAAAAAHH
HHHHHHHHHHH...hi :)
gcn_x86Apr 13, 2023
Show threadjacquelines 🌟Apr 13, 2023
@mos_8502
Show threadgcn_x86Apr 13, 2023
@mos_8502 I always chuckle whenever I think of this image. Hope it gets a chuckle out of you, too.
Show threadgcn_x86Apr 11, 2023
Mwahahaha.
gcn_x86Apr 11, 2023
Everything back in order. Now I can compile the os with optimizations on. Yay!
Show threadgcn_x86Apr 11, 2023
Insert feet in mouth. I'm just a ginormous, bloody idiot. k_int_Init calls k_int_Lidt, which loads the IDT. And k_int_Lidt isn't saving ebx. Nor eax. No wonder things go to shit. It doesn't crash when not optimizing because values are reloaded from the stack all the time.
Show threadgcn_x86Apr 11, 2023
This is the code it gets generated from. ebx is holding the init_data pointer. The null pointer check before the k_int_Init call is there because I was suspecting the bootloader was screwing up.
Show threadgcn_x86Apr 11, 2023
This is where the issue happens. At 0xe517 a pointer stored in the stack by the bootloader gets read into ebx. Before the call at 0xe520 the value is correct. After it it's some nonsense that crashes the kernel further down the road. This is at -O3.
gcn_x86Apr 11, 2023
Hmm, I wonder if undefined behavior would lead gcc to fail saving a register before a function call that clobbers it.
gcn_x86Apr 11, 2023
Fuck, I got them post-anime blues again...
Show threadgcn_x86Apr 6, 2023
@chjara They're neether.