4 ms·
Please note that: 1) The goals of Reload are very complex. http://gcc.gnu.org/wiki/reload http://gcc.gnu.org/wiki/reload "Reload does everything, and probabl
by acqq 12y ago
Please note that:
1) The goals of Reload are very complex.
http://gcc.gnu.org/wiki/reload http://gcc.gnu.org/wiki/reload
"Reload does everything, and probably no one exactly knows how much that is. But to give you some idea:
Spill code generation
Instruction/register constraint validation
Constant pool building
Turning non-strict RTL (Register Transfer Language, a very low level intermediate representation used in the backends of GCC) into strict RTL (doing more of the above in evil ways).
Register elimination--changing frame pointer references to stack pointer references
Reload inheritance--essentially a builtin CSE (Common Subexpression Elimination) pass on spill code"
Reload achieved them for the last 25 years(!)
2) There are more modern approaches to reach such goals, but knowing 1) it is a lot of work before the goals can be achieved by some alternative code for all platforms (I don't know how far the developers got at the moment)
3) "Local Register Allocator
Project" presentation by Vladimir Makarov, working for RedHat:
http://gcc.gnu.org/wiki/cauldron2012?action=AttachFile&do=get&target=Local_Register_Allocator_Project_Detail.pdf http://gcc.gnu.org/wiki/cauldron2012?action=AttachFile&do=ge...