Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Wow, something went really wrong here. For a long time I've been running two parallel builds of my kernel -- one that passes -D NDEBUG to gcc (my "free" build) and one without (my "checked" build). I added -O3 to the compiler settings for my free build, and suddenly my kernel binary grows from 23KB to 3GB!
I'm guessing there is something subtle that I don't understand about my linker script, since my kernel is linked to run in the higher half. Here it is:
Are there any magical sections I'm not aware of that would only show up when compiling with -O3 (or any of the -O's, they all do the same thing)? BTW, I'm using a gcc cross-compiler (built from gcc 3.4.1 sources according to the instructions on the OS FAQ).
Top three reasons why my OS project died:
Too much overtime at work
Got married
My brain got stuck in an infinite loop while trying to design the memory manager
Well i really don't know the answer but the same question was posted long back and i think it was answered by Pype.Clicker better he could give you the answer
;D ROFL. Just invoke my name and your kernel will automagically debug
For I am the mighty wizard of OS. How wizzy your OS is, the wizard has a wizzer for your for nothing is too wizzy for the wize wizard of OS. ;D