Linked by Hadrien Grasland on Fri 28th Jan 2011 20:37 UTC
OSNews, Generic OSes It's recently been a year since I started working on my pet OS project, and I often end up looking backwards at what I have done, wondering what made things difficult in the beginning. One of my conclusions is that while there's a lot of documentation on OS development from a technical point of view, more should be written about the project management aspect of it. Namely, how to go from a blurry "I want to code an OS" vision to either a precise vision of what you want to achieve, or the decision to stop following this path before you hit a wall. This article series aims at putting those interested in hobby OS development on the right track, while keeping this aspect of things in mind.
Permalink for comment 460201
To read all comments associated with this story, please click here.
RE[6]: Machine language or C
by Alfman on Sun 30th Jan 2011 03:23 UTC in reply to "RE[5]: Machine language or C"
Alfman
Member since:
2011-01-28

"Even to this day it's often easy to beat a compiler's output"

"I quite doubt that. There's been plenty of discussion of this and the general consensus nowadays is that it's really, really hard to beat atleast GCC's optimizations anymore."

I feel you've copied my phrase entirely out of context. I want to re-emphasize my point that c compilers are constrained to strict calling conventions which imply shifting more variables between registers and the stack than would be possible to do by hand.

I'm not blaming GCC or any other compiler for this, after all calling conventions are very important for both static and dynamic linking. However it can result in code which performs worse than if done by hand.

As for your last sentence, isn't the consensus that GCC output performs poorly compared to other commercial compilers such as intel's?

I would be interested in seeing a fair comparison.

Edited 2011-01-30 03:37 UTC

Reply Parent Score: 1