Bill Wendling 4cc4666268 Place the GEP instructions nearer to the instructions which use them. ...

GEP instructions are there for the compiler and shouldn't really output much
code (if any at all). When a GEP is stored in the entry block, Fast ISel (for
one) will not know that it could fold it into further uses. For instance, inside
of the EH handling code. This results in a lot of unnecessary spills and loads
which bloat code and slows down pretty much everything.
<rdar://problem/10694814>


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@149114 91177308-0d34-0410-b5e6-96231b3b80d8

2012-01-27 02:02:24 +00:00

..

Analysis

enhance constant folding to be able to constant fold bitcast of

2012-01-27 01:44:03 +00:00

Archive

Avoid using an invalidated iterator.

2012-01-23 05:07:16 +00:00

AsmParser

…

Bitcode

…

CodeGen

Place the GEP instructions nearer to the instructions which use them.

2012-01-27 02:02:24 +00:00

DebugInfo

…

ExecutionEngine

add more support for ConstantDataSequential

2012-01-24 13:41:11 +00:00

Linker

use Constant::getAggregateElement to simplify a bunch of code.

2012-01-25 06:48:06 +00:00

MC

Source information in 'expected relocatable expression' diagnostic.

2012-01-27 00:51:23 +00:00

Object

Sink assert-only variables into the asserts

2012-01-24 19:43:30 +00:00

Support

Tidy up. s/Low Level Virtual Machine/LLVM/.

2012-01-25 22:00:23 +00:00

TableGen

…

Target

Keep source location information for X86 MCFixup's.

2012-01-27 00:51:27 +00:00

Transforms

Continue improving support for ConstantDataAggregate, and use the

2012-01-26 02:32:04 +00:00

VMCore

smallvectorize and ArrayRef'ize some stuff.

2012-01-26 20:40:56 +00:00

CMakeLists.txt

…

LLVMBuild.txt

…

Makefile

…