llvm-svn: 37429

Thanks Chuck!

llvm-svn: 37428

llvm-svn: 37427

llvm-svn: 37426

the difference manually instead.

This allows GVNPRE to produce correct analysis for the example in the GVNPRE
paper.

llvm-svn: 37425

llvm-svn: 37424

This fixes PR1491 and GlobalOpt/2007-06-04-PackedStruct.ll

llvm-svn: 37423

llvm-svn: 37421

llvm-svn: 37420

llvm-svn: 37419

llvm-svn: 37418

llvm-svn: 37417

llvm-svn: 37415

and create new node.

llvm-svn: 37414

llvm-svn: 37413

that the CSE map always contains explicit alignment information. This allows
more loads to be CSE'd when there is a mix of explicit-alignment loads and
implicit-alignment loads.

Also, in SelectionDAG::FindModifiedNodeSlot, add the operands to the
FoldingSetNodeID before the load/store information instead of after, so
that it matches what is done elsewhere.

llvm-svn: 37411

llvm-svn: 37410

Let IfConverter loose. Allow more aggressive subsumptions; reorder basic blocks to expose more ifcvt opportunities; code clean up and fixes.

llvm-svn: 37409

llvm-svn: 37408

llvm-svn: 37407

llvm-svn: 37406

llvm-svn: 37405

llvm-svn: 37404

llvm-svn: 37403

llvm-svn: 37402

There's no need to have an Expression class... Value works just as well!  This simplifies a lot of code.

llvm-svn: 37401

switches.  There is one really easy isel thing here with tst we are not
getting.

llvm-svn: 37400

(landing pad) when an exception unwinds through the call.  This doesn't
quite match the way the dwarf unwinder works: by default it only jumps to
the landing pad if the catch or filter specification matches, and otherwise
it keeps on unwinding.  There are two ways of specifying to the unwinder
that it should "always" (more on why there are quotes here later) jump to
the landing pad: follow the specification by a 0 typeid, or follow it by
the typeid for the NULL typeinfo.  GCC does the first, and this patch makes
LLVM do the same as gcc.  However there is a problem: the unwinder performs
optimizations based on C++ semantics (it only expects destructors to be
run if the 0 typeid fires - known as "cleanups"), meaning it assumes that no
exceptions will be raised and that the raised exception will be reraised
at the end of the cleanup code.  So if someone writes their own LLVM code
using the exception intrinsics they will get a nasty surprise if they don't
follow these rules.  The other possibility of using the typeid corresponding
to NULL (catch-all) causes the unwinder to make no assumptions, so this is
probably what we should use in the long-run.  However since we are still
having trouble getting exception handling working properly, for the moment
it seems best to closely imitate GCC.

llvm-svn: 37399

simplifies the code in DwarfWriter, allows for multiple filters and
makes it trivial to specify filters accompanied by cleanups or catch-all
specifications (see next patch).  What a deal!  Patch blessed by Anton.

llvm-svn: 37398

llvm-svn: 37397

llvm-svn: 37394

llvm-svn: 37393

See test/CodeGen/X86/test-pic-jtbl.ll for a case where it works well;
shaves another 10K off our favorite benchmark.  I was hesitant about
this because of compile speed, but seems to do OK on a bootstrap.

llvm-svn: 37392

Avoid overwriting the APInt instance with 0 bytes which causes the bitwidth
to be set to 0 (illegal) producing a subsequent assert.

llvm-svn: 37391

llvm-svn: 37390

llvm-svn: 37389

llvm-svn: 37388

llvm-svn: 37387

llvm-svn: 37386

llvm-svn: 37385