Andrew Trick e89c19ab7b In the pre-RA scheduler, maintain cmp+br proximity. ... This is done by pushing physical register definitions close to their use, which happens to handle flag definitions if they're not glued to the branch. This seems to be generally a good thing though, so I didn't need to add a target hook yet. The primary motivation is to generate code closer to what people expect and rule out missed opportunity from enabling macro-op fusion. As a side benefit, we get several 2-5% gains on x86 benchmarks. There is one regression: SingleSource/Benchmarks/Shootout/lists slows down be -10%. But this is an independent scheduler bug that will be tracked separately. See rdar://problem/9283108. Incidentally, pre-RA scheduling is only half the solution. Fixing the later passes is tracked by: <rdar://problem/8932804> [pre-RA-sched] on x86, attempt to schedule CMP/TEST adjacent with condition jump Fixes: <rdar://problem/9262453> Scheduler unnecessary break of cmp/jump fusion llvm-svn: 129508		2011-04-14 05:15:06 +00:00
..
llvm	In the pre-RA scheduler, maintain cmp+br proximity.	2011-04-14 05:15:06 +00:00
llvm-c	Add the alias analysis to the C api.	2011-04-13 15:44:58 +00:00