Cool! Is there a specific reason why you do it this way? Smaller build time for the kernel itself?Combuster wrote: [...]
I actually have a sort of compiler in my OS source tree that gets built and then builds parts of my OSAntti wrote:I am quite sure that many OS developers are also interested in compilers(same with a runtime linker, of which I have two now)
The "kernel" is only worth one assembler command. The tool turns data definitions into code that reads and writes the data, as well as header files for various languages and implementation styles, so that there's only one place where the OS's primitives are used directly.Cool! Is there a specific reason why you do it this way? Smaller build time for the kernel itself?
I couldn't think of a good reason bu that makes a lot of sense. Cool approachCombuster wrote:The "kernel" is only worth one assembler command. The tool turns data definitions into code that reads and writes the data, as well as header files for various languages and implementation styles, so that there's only one place where the OS's primitives are used directly.Cool! Is there a specific reason why you do it this way? Smaller build time for the kernel itself?
Sorry for contradicting, but that's not what I think. It took me about 1h of brainless coding to get a working "Hello World" compiler, without reading anything about the topic. I'm not rich enough to be able to pay 260€ for the dragon book (that's good as I want to start from scratch without being influenced by other designs).muazzam wrote:Compiler development requires knowledge of Discrete mathematics, Automata theory, Logic etc.
Depends, writing a predictive recursive-descent parser is pretty simple. When you go into some more advanced topics (I think especially optimization) you're going to need some theory, I guess (I haven't really coded a compiler, but that's what I readno92 wrote:Sorry for contradicting, but that's not what I think. It took me about 1h of brainless coding to get a working "Hello World" compiler, without reading anything about the topic. I'm not rich enough to be able to pay 260€ for the dragon book (that's good as I want to start from scratch without being influenced by other designs).muazzam wrote:Compiler development requires knowledge of Discrete mathematics, Automata theory, Logic etc.
At some point, somebody who has some knowledge about this topic should create a wiki page explaining where and how to start, as (appearently) quite a few in the OSDev forums want to start CompilerDeving too.
).Code: Select all
$code = array(
new Token("f", array("hello_world")),
new Token("{", array()),
new Token("printf", array("%s %s!\\n", "Hello", "World")),
new Token("}", array()),
new Token("printf", array("Test\\n")),
new Token("hello_world", array())
);Code: Select all
$code = array(
new Function("hello_world", array(/*no arguments*/), array(
new CallExpression("printf", array(
new StringExpression("%s %s!\n"),
new StringExpression("Hello"),
new StringExpression("World")
))
),
new CallExpression("printf", array(new StringExpression("Test\n"))),
new CallExpression("hello_world", array())
)
. Any other suggestions/improvements (MessiahAndrw, I'm talking to you!)? It's still a WIP, so feel free to directly edit it, if you're sure your code/explanation/etc. is better.That is so true! For the dragon book, I think you can see it mainly as a reference. It is probably one of the more comprehensive works on compiler development. Don't expect too much hand-holding or implementation details. There are some sections devoted to 'the bigger picture', but the main part of the book consists of a systematic treatment of the available techniques and algorithms.MessiahAndrw wrote:I have the basics of a compiler down (lexers, grammars, abstract syntax trees, linking, simple stop-the-world garbage collector, SSA) - I took a course at university and figured the rest out online. But, information online is very scarce. There are research white papers, people's blogs, slideshow notes from college courses online - but they are usually really indepth and upclose - and you wish someone could stand back and give you the overall picture of how it fits in, or they're talking high level (how do I implement this!) and you understand the theory, but you really wish someone would kind of hint (not do it for you, but point you in the right direction to get started) at how you would implement this algorithm in a low level language.
Everyone seems to be pointing to the dragon book as the go-to reference guide, so I ordered myself a copy to see what the fuss is about.
It's probably not perfect on the first try, but actually starting to write something is sometimes the biggest problem. I'm willing to contribute, but I think I should get some more experience with building compilers first...It's looking good. I've thought about writing a section on language design, since I designed a compiler for my own language.no92 wrote:I'll probably reimplement it the way you proposed it, thanks alot
Heh, the first time I did write a compiler was yesterday ... nothing needed except for motivation and some basic theorykutkloon7 wrote: By the way, no92 and Combuster, really nice to see that people finally are creating something!
Yeah, I did dive in the theory some time ago, but it just got me stuck with more questions.no92 wrote:Heh, the first time I did write a compiler was yesterday ... nothing needed except for motivation and some basic theorykutkloon7 wrote: By the way, no92 and Combuster, really nice to see that people finally are creating something!