Writing a C compiler in 500 lines of Python
A few months ago, I set myself the challenge of writing a C compiler in 500 lines of Python1, after writing my SDF donut post. How hard could it be? The answer was, pretty hard, even when dropping quite a few features. But it was also pretty interesting, and the result is surprisingly functional and not too hard to understand! There's too much code for me to comprehensively cover in a single blog
Lessons from Writing a Compiler
The prototypical compilers textbook is: 600 pages on parsing theory. Three pages of type-checking a first-order type system like C. Zero pages on storing and checking the correctness of declarations (the “symbol tableâ€). Zero pages on the compilation model, and efficiently implementing separate compilation. 450 pages on optimization and code generation. The standard academic literature is most use
自作ã—ãŸRISC-Vå‘ã‘Cコンパイラã§ã‚»ãƒ«ãƒ•ãƒ›ã‚¹ãƒˆã¾ã§ã“ãŽã¤ã‘㟠- è©©ã¨å‰µä½œãƒ»æ€ç´¢ã®ã²ã‚ã°
低レイヤを知りãŸã„人ã®ãŸã‚ã®Cコンパイラ作æˆå…¥é–€ ã¾ã•ã«ä½Žãƒ¬ã‚¤ãƒ¤ã®ã“ã¨ãŒåˆ†ã‹ã£ã¦ãŠã‚‰ãšã€ä»¥å‰ã‹ã‚‰æ°—ã«ãªã£ã¦ã„ãŸã“ã®æœ¬ã€‚å–り掛ã‹ã£ã¦ã¿ãŸã¨ã“ã‚æ€ã„ã®ã»ã‹ã‚¹ã‚¤ã‚¹ã‚¤é€²ã‚られã¦ã€å‹¢ã„ã«ä¹—ã£ã¦ã‚»ãƒ«ãƒ•ãƒ›ã‚¹ãƒˆï¼ˆè‡ªåˆ†ãŒæ›¸ã„ãŸã‚³ãƒ³ãƒ‘イラã§è‡ªåˆ†è‡ªèº«ã‚’コンパイルã™ã‚‹ã¨ã“ã‚）ã¾ã§ã„ã‘ãŸã®ã§è¨˜å¿µã«æ›¸ã„ã¦ãŠã。æ£ç¢ºã«ã¯ C コンパイラã®ã‚µãƒ–セットã§ã™ã€‚ GitHub - motemen/mocc 全体的ãªé€²ã‚æ–¹ã¯ã€ 上記ã®æœ¬ã®é€šã‚Šã«é€²ã‚ã¦ã„ã。 ãれ以é™ã¯è‡ªä½œã® 8queen ãŒæ™®é€šã«æ›¸ã‘るよã†ã«æ©Ÿèƒ½ã‚’強化。 ãれ以é™ã¯ã‚»ãƒ«ãƒ•ãƒ›ã‚¹ãƒˆã‚’目標ã«é€²ã‚る。 プリプãƒã‚»ãƒƒã‚µã‚„リンカã¯ä½œã‚‰ãšã€C ã‹ã‚‰ã‚¢ã‚»ãƒ³ãƒ–リã¾ã§ã€‚ ã¨ã„ã†æ„Ÿã˜ã€‚自分ã¯æ‰‹ã‚’å‹•ã‹ã•ãªã„ã¨é€²ã‚“ã§ã‚‹æ°—ãŒã—ãªã„ã®ã§ã€ã¾ãšã¯æ›¸ã„ã¦ã¿ã¤ã¤ã‚ã‹ã‚‰ãªã„所ãŒã‚ã‚Œã°èª¿ã¹ã‚‹ã€ã¨ã„ã†ã‚¹ã‚¿ãƒ³ã‚¹ã§ã„ã。 ã‚ã¨ã€ã›ã£ã‹ããªã®ã§ RISC-V ã®å‹‰å¼·ã‚‚ã—ãŸã‹ã£ãŸã®ã§ã“ã‚Œå‘ã‘ã«æ›¸ã。ãªã®ã§å®Ÿè¡Œã¯
Brian Robert Callahan
academic, developer, with an eye towards a brighter techno-social life [prev] [next] 2021-08-14 Let's write a compiler, part 1: Introduction, selecting a language, and doing some planning All source code for this blog post can be found here. I think we all knew this might be coming once we finished up with our assembler. While we can in theory solve any computable problem by writing the appropriat
compiler - Vidar Hokstad V2.0 Rubyã§ã‚³ãƒ³ãƒ‘イラを書ããƒãƒ¥ãƒ¼ãƒˆãƒªã‚¢ãƒ«
(To follow my compiler related posts, either subscribe to my main RSS feed, or the compiler specific one ) Back in March 2008 I started publishing a series on how to write a compiler in Ruby, bottom up, that is, starting with the code generator and working my way up instead of the more traditional approach of writing the parser first. Here are the parts I've published on my blog so far. (The bits
1
ランã‚ング
ランã‚ング
メンテナンス
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Home - Playing with code
Flattening ASTs (and Other Compiler Data Structures)
コンパイラ演習レジュメ
{{#tags}}- {{label}}
{{/tags}}