This is the mail archive of the
mailing list for the GCC project.
- From: Paolo Bonzini <bonzini at gnu dot org>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, Kenneth Zadeck <zadeck at naturalbridge dot com>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, Richard dot Earnshaw at arm dot com, bonzini at gnu dot org, dave dot korn at artimi dot com, dje at watson dot ibm dot com, gcc at gcc dot gnu dot org, iant at google dot com, rsandifo at nildram dot co dot uk, stevenb dot gcc at gmail dot com
- Date: Mon, 09 Jul 2007 11:44:22 -0400
- Subject: Re: no_new_pseudos
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <10707091208.AA07438@vlsi1.ultra.nyu.edu> <469238A9.firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
I am going to argue that it was a bug that we did not allow new
pseudos after flow had ran. And that we should have always allowed
pseudos before the register allocator. Since flow was so broken, we
could not, we added the hack no_new_pseudos get around that problem.
Now we are saying it is a nice abstraction but I am saying this
abstraction should never have happened in the first place. We now
have a better compiler due to the removal of the hack.
The bad abstraction was causing quirks in *when* no_new_pseudos was set
to 1. But no_new_pseudos is a good abstraction in itself, people are
arguing on whether it is a better abstraction as "reload_in_progress ||