llvm-svn: 122340

llvm-svn: 122339

information caused token-annotation to fail in funny ways. Fixes
<rdar://problem/8595386>.

llvm-svn: 122338

llvm-svn: 122337

not very important since the pass is only used for testing, but it does make
it more realistic.  Suggested by Frits van Bommel.

llvm-svn: 122336

llvm-svn: 122335

type.

llvm-svn: 122334

llvm-svn: 122333

not assume this (for example in case more transforms get added below
it).  Suggested by Frits van Bommel.

llvm-svn: 122332

llvm-svn: 122331

plenty left though!), in particular for multiplication.

llvm-svn: 122330

llvm-svn: 122329

quite often, but don't make much difference in practice presumably because
instcombine also knows them and more.

llvm-svn: 122328

No functionality change.

llvm-svn: 122327

a couple of existing transforms.  This fires surprisingly often, for
example when compiling gcc "(X+(-1))+1->X" fires quite a lot as well
as various "and" simplifications (usually with a phi node operand).
Most of the time this doesn't make a real difference since the same
thing would have been done elsewhere anyway, eg: by instcombine, but
there are a few places where this results in simplifications that we
were not doing before.

llvm-svn: 122326

llvm-svn: 122325

clang_getCursorLexicalParent() to cope with class and function
templates, along with the parent of the translation unit. Fixes PR8761
and PR8766.

llvm-svn: 122324

looking in is complete. Fixes PR8756.

llvm-svn: 122323

checking trivial comparisons. Fixes PR8795.

llvm-svn: 122322

of the problems with my last attempt were in the updating of LiveIntervals
rather than the coalescing itself. Therefore, I decided to get that right first
by essentially reimplementing the existing PHIElimination using LiveIntervals.

It works correctly, with only a few tests failing (which may not be legitimate
failures) and no new verifier failures (at least as far as I can tell, I didn't
count the number per file).

llvm-svn: 122321

Type legalization splits up i64 values into pairs of i32 values, which leads
to poor quality code when inserting or extracting i64 vector elements.
If the vector element is loaded or stored, it can be treated as an f64 value
and loaded or stored directly from a VPR register.  Use the pre-legalization
DAG combiner to cast those vector elements to f64 types so that the type
legalizer won't mess them up.  Radar 8755338.

llvm-svn: 122319

llvm-svn: 122318

llvm-svn: 122317

the process.  The custom thread started before this point is running in a loop
waiting for events to come.

llvm-svn: 122316

llvm-svn: 122315

section.

This helps because in practice sections form a dag with debug sections pointing
to text sections. Finishing up the text sections first makes the debug section
relaxation trivial.

llvm-svn: 122314

Fixes rdar://8782223

llvm-svn: 122313

llvm-svn: 122312

Fix PR8832.

llvm-svn: 122311

something that just glues two nodes together, even if it is
sometimes used for flags.

llvm-svn: 122310

llvm-svn: 122309

llvm-svn: 122308

to be the one we want to use. bugpoint reduced testcase is a little large,
I'll see if I can simplify it down more.

Fixes part of rdar://8782207

llvm-svn: 122307

llvm-svn: 122306

they are just as useless, but at least a bit more gramatical

llvm-svn: 122305

debugger and to exercise some event APIs.

llvm-svn: 122304

tPseudoInst class, its size was changed from "special" to "2 bytes". This is
incorrect because the jump table will no longer be taken into account when
calculating branch offsets.
<rdar://problem/8782216>

llvm-svn: 122303

llvm-svn: 122302

Edge bundles is an annotation on the CFG that turns it into a bipartite directed
graph where each basic block is connected to an outgoing and an ingoing bundle.
These bundles are useful for identifying regions of the CFG for live range
splitting.

llvm-svn: 122301

in an exception specification.

llvm-svn: 122297