factor/basis/compiler/cfg/linear-scan
Slava Pestov db7403d697 compiler.cfg.linear-scan.resolve: fix incorrect behavior when one physical register is used with several representations in the same register class 2010-05-03 17:34:14 -04:00
..
allocation compiler.cfg.linear-scan: don't insert a _reload if the register is going to be overwritten anyway 2010-05-03 17:34:14 -04:00
assignment compiler.cfg.linear-scan: don't insert a _reload if the register is going to be overwritten anyway 2010-05-03 17:34:14 -04:00
debugger Making all of basis and extra unambiguous for sets/namespaces 2010-02-26 16:28:38 -05:00
live-intervals compiler.cfg.linear-scan: don't insert a _reload if the register is going to be overwritten anyway 2010-05-03 17:34:14 -04:00
numbering compiler.cfg.linearization.order: basic blocks were being inserted twice if some blocks had repeated successors, causing problems for register allocation 2009-09-22 03:19:23 -05:00
resolve compiler.cfg.linear-scan.resolve: fix incorrect behavior when one physical register is used with several representations in the same register class 2010-05-03 17:34:14 -04:00
linear-scan-tests.factor compiler.cfg.linear-scan: don't insert a _reload if the register is going to be overwritten anyway 2010-05-03 17:34:14 -04:00
linear-scan.factor compiler.cfg: new system to track when results of analyses need to be recomputed (reverse post order, linear order, predecessors, dominance, loops). Passes can now call needs-predecessors, needs-dominance, needs-loops at the beginning, and cfg-changed, predecessors-changd at the end. Linearization order now takes loop nesting into account, and linear scan now uses linearization order instead of RPO. 2009-08-08 20:02:56 -05:00
summary.txt