| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
the code to annotate machineoperands to LiveIntervalAnalysis. It also add markers for implicit_def that define physical registers. The rest, is just a lot of details.
llvm-svn: 74580
|
|
|
|
|
|
|
| |
- This more or less amounts to a revert of r65379. I'm curious to know what
happened that caused this variable to become unused.
llvm-svn: 74579
|
|
|
|
| |
llvm-svn: 74577
|
|
|
|
| |
llvm-svn: 74574
|
|
|
|
| |
llvm-svn: 74566
|
|
|
|
|
|
|
|
|
|
| |
have the alignment be calculated up front, and have the back-ends obey whatever
alignment is decided upon.
This allows for future work that would allow for precise no-op placement and the
like.
llvm-svn: 74564
|
|
|
|
| |
llvm-svn: 74555
|
|
|
|
| |
llvm-svn: 74551
|
|
|
|
|
|
| |
in APIntTest.cpp.
llvm-svn: 74550
|
|
|
|
| |
llvm-svn: 74549
|
|
|
|
| |
llvm-svn: 74548
|
|
|
|
| |
llvm-svn: 74543
|
|
|
|
| |
llvm-svn: 74542
|
|
|
|
| |
llvm-svn: 74537
|
|
|
|
|
|
|
| |
Avoid unnecessary duplication of operand 0 of X86::FpSET_ST0_80. This duplication would
cause one register to remain on the stack at the function return.
llvm-svn: 74534
|
|
|
|
|
|
|
|
| |
See http://msdn.microsoft.com/en-us/library/ms686818(VS.85).aspx
Patch by Olaf Krzikalla!
llvm-svn: 74526
|
|
|
|
|
|
| |
This was caused by me confounding FP0 and ST(0).
llvm-svn: 74523
|
|
|
|
|
|
| |
isUndef mark is not being put on implicit_def of physical registers (created for parameter passing, etc.).
llvm-svn: 74519
|
|
|
|
|
|
|
|
|
|
| |
operand is defined by an implicit_def. That means it can def / use any register and passes (e.g. register scavenger) can feel free to ignore them.
The register allocator, when it allocates a register to a virtual register defined by an implicit_def, can allocate any physical register without worrying about overlapping live ranges. It should mark all of operands of the said virtual register so later passes will do the right thing.
This is not the best solution. But it should be a lot less fragile to having the scavenger try to track what is defined by implicit_def.
llvm-svn: 74518
|
|
|
|
| |
llvm-svn: 74515
|
|
|
|
| |
llvm-svn: 74510
|
|
|
|
| |
llvm-svn: 74509
|
|
|
|
| |
llvm-svn: 74508
|
|
|
|
| |
llvm-svn: 74507
|
|
|
|
| |
llvm-svn: 74500
|
|
|
|
| |
llvm-svn: 74499
|
|
|
|
|
|
|
| |
This will allow it to be used in unittests that use gtest's
EXPECT_EQ.
llvm-svn: 74494
|
|
|
|
| |
llvm-svn: 74492
|
|
|
|
| |
llvm-svn: 74491
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Don't print "Parsing" in front of every message.
- Take additional "type" argument which is prepended to the message (with ": ")
if given.
- Update clients to print errors (warnings) as:
<filename>:<line number>: error(warning): ...
llvm-svn: 74489
|
|
|
|
|
|
|
|
| |
privatizing a lot of (currently) global state, including the
constant and type uniquing tables. For now, just make it a wrapper around the existing APIs.
llvm-svn: 74488
|
|
|
|
| |
llvm-svn: 74483
|
|
|
|
| |
llvm-svn: 74482
|
|
|
|
| |
llvm-svn: 74478
|
|
|
|
| |
llvm-svn: 74477
|
|
|
|
| |
llvm-svn: 74473
|
|
|
|
| |
llvm-svn: 74469
|
|
|
|
| |
llvm-svn: 74468
|
|
|
|
|
|
|
|
|
|
| |
Constant. This lets ConstantInts be handled as SCEVConstant instead
of SCEVUnknown, as getUnknown no longer has special-case code for
ConstantInt and friends. This usually doesn't affect the final
output, since the constants end up getting folded later, but it
does make intermediate expressions more obvious in many cases.
llvm-svn: 74459
|
|
|
|
|
|
| |
module support to build).
llvm-svn: 74456
|
|
|
|
| |
llvm-svn: 74455
|
|
|
|
| |
llvm-svn: 74452
|
|
|
|
|
|
| |
Update dwarf writer to only emit one DW_TAG_compile_unit per .o file.
llvm-svn: 74449
|
|
|
|
|
|
|
|
| |
an individual exhaustive evaluation reflects only the exit value
implied by an individual exit, which may differ from the actual
exit value of the loop if there are other exits. This fixes PR4477.
llvm-svn: 74447
|
|
|
|
|
|
|
| |
Not sure I understand how the temp register gets used,
but this fixes a bug and introduces no regressions.
llvm-svn: 74446
|
|
|
|
|
|
| |
Not doing so causes some unittests to fail, because CurSection is uninitialized.
llvm-svn: 74442
|
|
|
|
| |
llvm-svn: 74440
|
|
|
|
| |
llvm-svn: 74439
|
|
|
|
|
|
|
|
|
|
| |
on-the-fly passes as well.
Also don't call finalizers for LoopPass if initialization was not called.
Add a unittest that tests that these methods are called, in the proper
order, and the correct number of times.
llvm-svn: 74438
|
|
|
|
|
|
|
| |
(otherwise harmless) uninitialized value warnings that
Duncan found with gcc-4.4.
llvm-svn: 74437
|