Re: Help on code generation and register allocation

russell kym horsell <kym@ukato.freeshell.org>
11 Feb 2006 13:14:54 -0500

          From comp.compilers

Related articles
Help on code generation and register allocation Forum.Thomas.Krause@gmx.de (Thomas Krause) (2006-02-07)
Re: Help on code generation and register allocation d148f3wg02@sneakemail.com (Karsten Nyblad) (2006-02-11)
Re: Help on code generation and register allocation kym@ukato.freeshell.org (russell kym horsell) (2006-02-11)
Re: Help on code generation and register allocation avayvod@gmail.com (Whywhat) (2006-02-11)
Re: Help on code generation and register allocation u.hobelmann@web.de (Ulrich Hobelmann) (2006-02-12)
Re: Help on code generation and register allocation avayvod@gmail.com (Whywhat) (2006-02-14)
Re: Help on code generation and register allocation u.hobelmann@web.de (Ulrich Hobelmann) (2006-02-14)
Re: Help on code generation and register allocation torbenm@app-5.diku.dk (2006-02-17)
Re: Help on code generation and register allocation boldyrev@cgitftp.uiggm.nsc.ru (Ivan Boldyrev) (2006-02-17)
[2 later articles]
| List of all articles for this month |

From: russell kym horsell <kym@ukato.freeshell.org>
Newsgroups: comp.compilers
Date: 11 Feb 2006 13:14:54 -0500
Organization: Central Iowa (Model) Railroad, Plano, TX, USA
References: 06-02-055
Keywords: registers

Thomas Krause <Forum.Thomas.Krause@gmx.de> wrote:
> Hello,
> I need help writing my compiler. The front end stuff (parsing, etc.)
> is not the problem, but the back end is.
> 1.) My idea is to first build a forrest of expression trees for the
> parsed code, then map the nodes of the tree to the registers of my
> target architecture (X86) and then produce the code. But as simple as
> its sounds I don't know really how I should do that.




Maybe look into "list scheduling of basic blocks" and think about allocating
the registers and peeholes and fixups in later phases.
If you're trying for "optimal register usage" like many of the other folks
around here, you have to walk first. ;-)



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.