Re: Register allocation

sumesh_uk@hotmail.com (sumesh)
31 Jul 2003 12:46:37 -0400

          From comp.compilers

Related articles
Register allocation sumesh_uk@hotmail.com (2003-07-04)
Re: Register allocation touati@prism.uvsq.fr (TOUATI Sid) (2003-07-15)
Register allocation robert.thorpe@antenova.com (Rob Thorpe) (2003-07-21)
Re: Register allocation sumesh_uk@hotmail.com (2003-07-21)
Re: Register allocation lindahl@pbm.com (2003-07-21)
Re: Register allocation dany42NOSPAM@free.fr (Dan) (2003-07-21)
Re: Register allocation sumesh_uk@hotmail.com (2003-07-31)
Register allocation avizit@gmail.com (2004-07-15)
Re: Register allocation gopi@sankhya.com (2004-07-28)
Re: Register allocation rajaram@acmet.com (Rajaram) (2004-08-04)
Re: Register allocation kamalp@acm.org (2004-08-05)
Re: Register allocation kym@sdf.lonestar.org (russell kym horsell) (2004-08-09)
Re: Register allocation kamalp@acm.org (2004-08-09)
[22 later articles]
| List of all articles for this month |
From: sumesh_uk@hotmail.com (sumesh)
Newsgroups: comp.compilers
Date: 31 Jul 2003 12:46:37 -0400
Organization: http://groups.google.com/
References: 03-07-058 03-07-097 03-07-140 03-07-162
Keywords: registers
Posted-Date: 31 Jul 2003 12:46:37 EDT

I recently found out this ....what I was looking for is called
loads/store hoisting and is available on gcc 2.9.5. It moves redudant
loada/stores out of a loop.
-Sumesh




Dan <dany42NOSPAM@free.fr> wrote
> Rob Thorpe <robert.thorpe@antenova.com> writes:
>
> > As far as I know GCC compiles on a per file basis at present. So it
> > can't make decisions like placing globals into registers. It's not a
> > particularly useful optimization anyway, unless there are many
> > registers.
>
> If you want more infos about how register allocation is processed in
> GCC you can read Michael Matz paper: «Design and implementation of the
> graph coloring register allocator for GCC».
>
> It is avaible at the following url:
> http://www.linux.org.uk/~ajh/gcc/gccsummit-2003-proceedings.pdf



Post a followup to this message

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