| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
non-const.
llvm-svn: 108734
|
| |
|
|
|
|
| |
Do not try to insert local variable info to a DIE used for function declaration.
llvm-svn: 108731
|
| |
|
|
| |
llvm-svn: 108700
|
| |
|
|
|
|
|
|
| |
pressure estimates and liveness alongside.
Still experimental.
llvm-svn: 108698
|
| |
|
|
| |
llvm-svn: 108688
|
| |
|
|
|
|
| |
- Unfortunate, but necessary for now to handle subtarget instruction matching. Eventually we should factor out the lower level target machine information so we don't need to do this.
llvm-svn: 108664
|
| |
|
|
| |
llvm-svn: 108645
|
| |
|
|
| |
llvm-svn: 108642
|
| |
|
|
|
|
|
|
|
|
| |
conversions around sqrt instructions.
I am assured by people more knowledgeable than me that there are no rounding issues in eliminating this.
This fixed <rdar://problem/8197504>.
llvm-svn: 108639
|
| |
|
|
|
|
|
|
|
|
| |
require
LoopSplitter be run prior to register allocation.
Entirely for testing purposes at the moment.
llvm-svn: 108634
|
| |
|
|
| |
llvm-svn: 108628
|
| |
|
|
| |
llvm-svn: 108620
|
| |
|
|
| |
llvm-svn: 108618
|
| |
|
|
|
|
|
|
| |
Still very much under development. Comments and fixes will be forthcoming.
(This commit includes some small tweaks to LiveIntervals & LoopInfo to support the splitter)
llvm-svn: 108615
|
| |
|
|
|
|
|
|
|
|
|
| |
any command line paramater changed the register allocation produced by
PBQP.
Turns out variety is not the spice of life.
Fixed some comparators, added others. All good now.
llvm-svn: 108613
|
| |
|
|
|
|
|
|
| |
information.
No functional change yet.
llvm-svn: 108583
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
void foo() { __builtin_unreachable(); }
It will output the following on Darwin X86:
_func1:
Leh_func_begin0:
pushq %rbp
Ltmp0:
movq %rsp, %rbp
Ltmp1:
Leh_func_end0:
This prolog adds a new Call Frame Information (CFI) row to the FDE with an
address that is not within the address range of the code it describes -- part is
equal to the end of the function -- and therefore results in an invalid EH
frame. If we emit a nop in this situation, then the CFI row is now within the
address range.
llvm-svn: 108568
|
| |
|
|
|
|
| |
thus is a much more meaningful name.
llvm-svn: 108563
|
| |
|
|
| |
llvm-svn: 108556
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
since it doesn't work for front-ends which don't emit column information
(which includes llvm-gcc in its present configuration), and doesn't
work for clang for K&R style variables where the variables are declared
in a different order from the parameter list.
Instead, make a separate pass through the instructions to collect the
llvm.dbg.declare instructions in order. This ensures that the debug
information for variables is emitted in this order.
llvm-svn: 108538
|
| |
|
|
| |
llvm-svn: 108520
|
| |
|
|
|
|
| |
TII::isMoveInstr is going tobe completely removed.
llvm-svn: 108507
|
| |
|
|
|
|
|
| |
because it's more likely to keep debug line information in its original
order.
llvm-svn: 108496
|
| |
|
|
|
|
|
|
|
|
| |
occasions, caused code to be generated in a different order.
All cases I've seen involved float softening in the type
legalizer, and this could be perhaps be fixed there, but
it's better not to generate things differently in the first
place. 7797940 (6/29/2010..7/15/2010).
llvm-svn: 108484
|
| |
|
|
| |
llvm-svn: 108478
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the function. We'll just turn it into a "trap" instruction instead.
The problem with not handling this is that it might generate a prologue without
the equivalent epilogue to go with it:
$ cat t.ll
define void @foo() {
entry:
unreachable
}
$ llc -o - t.ll -relocation-model=pic -disable-fp-elim -unwind-tables
.section __TEXT,__text,regular,pure_instructions
.globl _foo
.align 4, 0x90
_foo: ## @foo
Leh_func_begin0:
## BB#0: ## %entry
pushq %rbp
Ltmp0:
movq %rsp, %rbp
Ltmp1:
Leh_func_end0:
...
The unwind tables then have bad data in them causing all sorts of problems.
Fixes <rdar://problem/8096481>.
llvm-svn: 108473
|
| |
|
|
|
|
| |
-enable-no-nans-fp-math and -enable-no-infs-fp-math. All of the current codegen fp math optimizations only care whether the fp arithmetics arguments and results can never be NaN.
llvm-svn: 108465
|
| |
|
|
|
|
|
|
|
|
|
| |
to keep "Text" in sync with the "pure instructions" section attribute.
Lack of this attribute was preventing the assembler from emitting
multibyte noops instructions for templates (and inlines, and other
coalesced stuff) and was causing the assembler to mismatch .o files.
This fixes rdar://8018335
llvm-svn: 108461
|
| |
|
|
| |
llvm-svn: 108452
|
| |
|
|
| |
llvm-svn: 108450
|
| |
|
|
|
|
| |
make sure to allocate enough space in the std::vector.
llvm-svn: 108449
|
| |
|
|
| |
llvm-svn: 108448
|
| |
|
|
| |
llvm-svn: 108441
|
| |
|
|
| |
llvm-svn: 108440
|
| |
|
|
| |
llvm-svn: 108438
|
| |
|
|
| |
llvm-svn: 108419
|
| |
|
|
| |
llvm-svn: 108413
|
| |
|
|
|
|
| |
get *very* large, but we only need it to be the size of the number of pregs.
llvm-svn: 108412
|
| |
|
|
|
|
| |
get *very* large, but we only need it to be the size of thenumber of pregs.
llvm-svn: 108411
|
| |
|
|
|
|
| |
follow on to r103765
llvm-svn: 108390
|
| |
|
|
| |
llvm-svn: 108381
|
| |
|
|
|
|
|
|
| |
independent of the order that isel happens to visit the dbg_declare
intrinsics. This fixes a bug in which the formal arguments were
being printed in reverse order, now that fast isel is going bottom up.
llvm-svn: 108369
|
| |
|
|
| |
llvm-svn: 108364
|
| |
|
|
|
|
| |
it can look past points where a debugger might modify user variables.
llvm-svn: 108336
|
| |
|
|
|
|
| |
IMPLICIT_DEF (and subsequently eliminate them). This allows machine LICM to hoist IMPLICIT_DEF's. PR7620.
llvm-svn: 108304
|
| |
|
|
|
|
|
| |
constants, since they may not be emited near the other instructions
which get the same line, and this confuses debug info.
llvm-svn: 108302
|
| |
|
|
| |
llvm-svn: 108277
|
| |
|
|
|
|
|
| |
This may not be right in all cases, but it's better
than asserting which it was doing before. PR 7528.
llvm-svn: 108268
|
| |
|
|
|
|
|
|
|
|
| |
LiveInterval::overlapsFrom dereferences end() if it is called on an empty
interval.
It would be reasonable to just return false - an empty interval doesn't overlap
anything, but I want to know who is doing it first.
llvm-svn: 108264
|
| |
|
|
|
|
| |
Also, one binary search is enough.
llvm-svn: 108261
|