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.
Thread beginning with comment 460205
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Machine language or C
by Alfman on Sun 30th Jan 2011 05:53 UTC in reply to "RE[7]: Machine language or C"
Member since:

Thinking about it further... the GCC bottleneck may not be the compiler at all but just the malloc implementation.

In an earlier post, I had mentioned that I made my own malloc which performs much better than GNU's malloc in multithreaded apps.

I think my implementation fits somewhere between ptmalloc and Hoard on the following chart.

I developed mine from scratch, so I have no idea why GNU's malloc is slow, but I'm baffled as to why GNU continues to use a slow implementation?

Reply Parent Score: 1