| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instruction are killed, but the first operand has a use before and after the def, commute if the second operand does not suffer from the same issue.
%reg1028<def> = EXTRACT_SUBREG %reg1027<kill>, 1
%reg1029<def> = MOV8rr %reg1028
%reg1029<def> = SHR8ri %reg1029, 7, %EFLAGS<imp-def,dead>
insert => %reg1030<def> = MOV8rr %reg1028
%reg1030<def> = ADD8rr %reg1028<kill>, %reg1029<kill>, %EFLAGS<imp-def,dead>
In this case, it might not be possible to coalesce the second MOV8rr
instruction if the first one is coalesced. So it would be profitable to
commute it:
%reg1028<def> = EXTRACT_SUBREG %reg1027<kill>, 1
%reg1029<def> = MOV8rr %reg1028
%reg1029<def> = SHR8ri %reg1029, 7, %EFLAGS<imp-def,dead>
insert => %reg1030<def> = MOV8rr %reg1029
%reg1030<def> = ADD8rr %reg1029<kill>, %reg1028<kill>, %EFLAGS<imp-def,dead>
llvm-svn: 62954
|
| |
|
|
| |
llvm-svn: 62940
|
| |
|
|
| |
llvm-svn: 62917
|
| |
|
|
| |
llvm-svn: 62893
|
| |
|
|
|
|
|
|
|
|
|
|
| |
DW_AT_APPLE_flags.
DW_AT_APPLE_optimized flag is set when a compile_unit is optimized. The debugger takes advantage of this information some way.
DW_AT_APPLE_flags encodes command line options when certain env. variable is set. This is used by build engineers to track various gcc command lines used by by a project, irrespective of whether the project used makefile, Xcode or something else.
llvm-gcc patch is next.
llvm-svn: 62888
|
| |
|
|
| |
llvm-svn: 62861
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
testcase from PR3376, and in fact is sufficient to completely
avoid the problem in that testcase.
There's an underlying problem though; TLI.isOperationLegal
considers Custom to be Legal, which might be ok in some
cases, but that's what DAGCombiner is using in many places
to test if something is legal when LegalOperations is true.
When DAGCombiner is running after legalize, this isn't
sufficient. I'll address this in a separate commit.
llvm-svn: 62860
|
| |
|
|
|
|
| |
restrictive register class.
llvm-svn: 62837
|
| |
|
|
|
|
|
|
|
|
| |
restores that are just
going to be re-spilled again.
This also helps performance. Pre-alloc-splitting now seems to be an overall win on SPEC.
llvm-svn: 62834
|
| |
|
|
| |
llvm-svn: 62832
|
| |
|
|
| |
llvm-svn: 62828
|
| |
|
|
| |
llvm-svn: 62827
|
| |
|
|
| |
llvm-svn: 62821
|
| |
|
|
|
|
| |
compatibility with VC++. Patch by Max Burke!
llvm-svn: 62813
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to "C ^ 1" is only valid when C is known to be either 0 or 1. Most of the
similar foldings in this function only handle "i1" types, but this one appears
intentionally written to handle larger integer types. If C has an integer
type larger than "i1", this needs to check if the high bits of a boolean
are known to be zero. I also changed the comment to describe this folding as
"C ^ 1" instead of "~C", since that is what the code does and since the latter
would only be valid for "i1" types. The good news is that most LLVM targets
use TargetLowering::ZeroOrOneBooleanContent so this change will not disable
the optimization; the bad news is that I've been unable to come up with a
testcase to demonstrate the problem.
I have also removed a "FIXME" comment for folding "select C, X, 0" to "C & X",
since the code looks correct to me. It could be made more aggressive by not
limiting the type to "i1", but that would then require checking for
TargetLowering::ZeroOrNegativeOneBooleanContent. Similar changes could be
done for the other SELECT foldings, but it was decided to be not worth the
trouble and complexity (see e.g., r44663).
llvm-svn: 62790
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Simplify x+0 to x in unsafe-fp-math mode. This avoids a bunch of
redundant work in many cases, because in unsafe-fp-math mode,
ISD::FADD with a constant is considered free to negate, so the
DAGCombiner often negates x+0 to -0-x thinking it's free, when
in reality the end result is -x, which is more expensive than x.
Also, combine x*0 to 0.
This fixes PR3374.
llvm-svn: 62789
|
| |
|
|
|
|
|
| |
corresponding to the "not" and "vnot" PatFrags. Use the new method
in some places where it seems appropriate.
llvm-svn: 62768
|
| |
|
|
| |
llvm-svn: 62763
|
| |
|
|
|
|
| |
SuperRegClasses. These are not necessary. Also eliminate getSubRegisterRegClass and getSuperRegisterRegClass. These are slow and their results can change if register file names change. Just use TargetLowering::getRegClassFor() to get the right TargetRegisterClass instead.
llvm-svn: 62762
|
| |
|
|
| |
llvm-svn: 62761
|
| |
|
|
|
|
|
|
| |
special cases after producing the new reduced-width load, because the
new load already has the needed adjustments built into it. This fixes
several bugs due to the special cases, including PR3317.
llvm-svn: 62692
|
| |
|
|
|
|
|
| |
prototypes, in operand type legalization. No
functionality change.
llvm-svn: 62680
|
| |
|
|
|
|
| |
in the pre alloc splitter.
llvm-svn: 62678
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Ensure that (operation) legalization emits proper FDIV libcall when needed.
- Fix various bugs encountered during llvm-spu-gcc build, along with various
cleanups.
- Start supporting double precision comparisons for remaining libgcc2 build.
Discovered interesting DAGCombiner feature, which is currently solved via
custom lowering (64-bit constants are not legal on CellSPU, but DAGCombiner
insists on inserting one anyway.)
- Update README.
llvm-svn: 62664
|
| |
|
|
|
|
| |
multiple values. For example, a load with an illegal operand (a load produces two values, a value and chain).
llvm-svn: 62663
|
| |
|
|
| |
llvm-svn: 62639
|
| |
|
|
| |
llvm-svn: 62638
|
| |
|
|
| |
llvm-svn: 62625
|
| |
|
|
|
|
| |
the last reference is also the last def (i.e. dead def), it should also check if last reference is the current machine instruction being processed. This can happen when it is processing a physical register use and setting the current machine instruction as sub-register's last ref.
llvm-svn: 62617
|
| |
|
|
|
|
|
| |
causing the limited precision stuff to produce the wrong result for values in
the range [0, 1).
llvm-svn: 62615
|
| |
|
|
| |
llvm-svn: 62610
|
| |
|
|
| |
llvm-svn: 62602
|
| |
|
|
|
|
| |
sub-register indices as well.
llvm-svn: 62600
|
| |
|
|
| |
llvm-svn: 62596
|
| |
|
|
| |
llvm-svn: 62594
|
| |
|
|
| |
llvm-svn: 62589
|
| |
|
|
| |
llvm-svn: 62573
|
| |
|
|
| |
llvm-svn: 62571
|
| |
|
|
|
|
|
| |
as its comment says, even in the case where it will be generating
extending loads. This fixes PR3216.
llvm-svn: 62557
|
| |
|
|
|
|
| |
types. After all there was a reason why std::map was used initially!
llvm-svn: 62555
|
| |
|
|
| |
llvm-svn: 62547
|
| |
|
|
| |
llvm-svn: 62545
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
SDNode subclasses to keep state that requires non-trivial
destructors, however it was already effectively impossible,
since the destructor isn't actually ever called. There currently
aren't any SDNode subclasses affected by this, and in general
it's desireable to keep SDNode objects light-weight.
This eliminates the last virtual member function in the SDNode
class, so it eliminates the need for a vtable pointer, making
SDNode smaller.
llvm-svn: 62539
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
uses are added to the From node while it is processing From's
use list, because of automatic local CSE. The fix is to avoid
visiting any new uses.
Fix a few places in the DAGCombiner that assumed that after
a RAUW call, the From node has no users and may be deleted.
This fixes PR3018.
llvm-svn: 62533
|
| |
|
|
| |
llvm-svn: 62467
|
| |
|
|
| |
llvm-svn: 62459
|
| |
|
|
| |
llvm-svn: 62423
|
| |
|
|
| |
llvm-svn: 62421
|
| |
|
|
| |
llvm-svn: 62412
|
| |
|
|
| |
llvm-svn: 62410
|