llvm-svn: 81541

object, the timer it creates was not being deleted.  Since the
timer belonged to a static timer group, the timer group would
be destroyed on shutdown, and would notice and complain that
not all timers it contained were destroyed.

llvm-svn: 81533

llvm-svn: 81532

llvm-svn: 81530

llvm-svn: 81517

llvm-svn: 81516

llvm-svn: 81514

densemap instead of StringMap to match FnStubs.

llvm-svn: 81513

more efficient SmallPtrSet<MCSymbol*>.  This eliminates string
craziness and fixes CodeGen/X86/darwin-quote.ll with the new asmprinter.

Codegen is producing stubs in a nondeterminstic order, but it was doing
this before anyway.

llvm-svn: 81511

for the two instruction MOVPC32r sequence.

llvm-svn: 81509

Mangler::getNameWithPrefix.  In addition to avoiding some over
quoting, this also is more efficient because it uses smallvector
instead of std::string thrashing.

llvm-svn: 81508

llvm-svn: 81506

(uniqued if unnamed) global variable name with the prefix that
it is supposed to get.  It doesn't do "mangling" in the sense of
adding quotes and hacking on bad characters.

llvm-svn: 81505

instead of std::string and Mangler.

llvm-svn: 81503

llvm-svn: 81502

Follow up to 81494. When the folded reload is narrowed to a 32-bit load then change the destination register to a 32-bit one or add a sub-register index.

llvm-svn: 81496

It's not legal to fold a load from a narrower stack slot into a wider instruction. If done, the instruction does a 64-bit load and that's not
safe. This can happen we a subreg_to_reg 0 has been coalesced. One
exception is when the instruction that folds the load is a move, then we
can simply turn it into a 32-bit load from the stack slot.                                                                                                                    

rdar://7170444

llvm-svn: 81494

llvm-svn: 81493

isn't legal.

llvm-svn: 81492

llvm-svn: 81484

how to fold notionally-out-of-bounds array getelementptr indices instead
of just doing these in lib/Analysis/ConstantFolding.cpp, because it can
be done in a fairly general way without TargetData, and because not all
constants are visited by lib/Analysis/ConstantFolding.cpp. This enables
more constant folding.

Also, set the "inbounds" flag when the getelementptr indices are
one-past-the-end.

llvm-svn: 81483

within the notional bounds of the static type of the getelementptr (which
is not the same as "inbounds") from GlobalOpt into a utility routine,
and use it in ConstantFold.cpp to check whether there are any mis-behaved
indices.

llvm-svn: 81478

llvm-svn: 81473

llvm-svn: 81468

post-decrement load/store.

llvm-svn: 81464

llvm-svn: 81463

that things like .word can be parsed as target specific.  Moved parsing .word
out of AsmParser.cpp into X86AsmParser.cpp as it is 2 bytes on X86 and 4 bytes
for other targets that support the .word directive.

llvm-svn: 81461

llvm-svn: 81459

various widths.

llvm-svn: 81458

including segment offsets and (for 8-bit operands)
absolute offsets.

llvm-svn: 81457

ones capable of accessing R/M operands instead of just
registers.

llvm-svn: 81456

llvm-svn: 81454

llvm-svn: 81450

llvm-svn: 81443

llvm-svn: 81438

used by a terminator in another.

llvm-svn: 81437

llvm-svn: 81436

from the exception tables. However, Duncan explained why it's a can of worms to
do it the GCC way. I went back to doing it the LLVM way and added Duncan's
explanation so that I don't do this again in the future.

llvm-svn: 81434

llvm-svn: 81426

like what GCC outputs. The mysterious code to insert padding wasn't in GCC at
all. I modified the TType base offset code to calculate the offset like GCC
does, though.

llvm-svn: 81424