| Commit message (Collapse) | Author | Age | Files | Lines | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
The alignment of allocated space was wrong, see Bugzila 17345.
Done by Zvi Rackover <zvi.rackover@intel.com>.
llvm-svn: 192573
 | 
| | 
| 
| 
| 
| 
|  | 
(This is triggered by current lit tests)
llvm-svn: 192549
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
The form must be a reference form in addDIEEntry. Which reference form to
use will be decided by the callee.
No functionality change.
llvm-svn: 192517
 | 
| | 
| 
| 
|  | 
llvm-svn: 192492
 | 
| | 
| 
| 
|  | 
llvm-svn: 192487
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
When if converting something like:
true:
   ... = R0<kill>
false:
   ... = R0<kill>
then the instructions of the true block must not have a <kill> flag
anymore, as the instruction of the false block follow and do still read
the R0 value.
Specifically this patch determines the set of register live-in in the
false block (possibly after simulating the liveness changes of the
duplicated instructions). Each of these live-in registers mustn't be
killed.
llvm-svn: 192482
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
sse4.2 support.
This should fix the buildbots.
Original commit message:
[DAGCombiner] Slice a big load in two loads when the element are next to each
other in memory and the target has paired load and performs post-isel loads
combining.
E.g., this optimization will transform something like this:
a = load i64* addr
b = trunc i64 a to i32
c = lshr i64 a, 32
d = trunc i64 c to i32
into:
b = load i32* addr1
d = load i32* addr2
Where addr1 = addr2 +/- sizeof(i32), if the target supports paired load and
performs post-isel loads combining.
One should overload TargetLowering::hasPairedLoad to provide this information.
The default is false.
<rdar://problem/14477220>
llvm-svn: 192476
 | 
| | 
| 
| 
| 
| 
|  | 
on ubuntu.
llvm-svn: 192474
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
other in memory and the target has paired load and performs post-isel loads
combining.
E.g., this optimization will transform something like this:
 a = load i64* addr
 b = trunc i64 a to i32
 c = lshr i64 a, 32
 d = trunc i64 c to i32
into:
 b = load i32* addr1
 d = load i32* addr2
Where addr1 = addr2 +/- sizeof(i32), if the target supports paired load and
performs post-isel loads combining.
One should overload TargetLowering::hasPairedLoad to provide this information.
The default is false.
<rdar://problem/14477220>
llvm-svn: 192471
 | 
| | 
| 
| 
|  | 
llvm-svn: 192455
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
comments for implicit defs
For NVPTX, this fixes a crash where the emitImplicitDef implementation was expecting physical registers,
while NVPTX uses virtual registers (with a couple of exceptions).  Now, the implicit def comment will be
emitted as a true PTX register name. Other targets can use this to customize the output of implicit def
comments.
Fixes PR17519
llvm-svn: 192444
 | 
| | 
| 
| 
| 
| 
|  | 
[-Wdocumentation]
llvm-svn: 192421
 | 
| | 
| 
| 
|  | 
llvm-svn: 192398
 | 
| | 
| 
| 
| 
| 
| 
|  | 
Previously LiveInterval has been used, but having a spill weight and
register number is unnecessary for a register unit.
llvm-svn: 192397
 | 
| | 
| 
| 
| 
| 
| 
|  | 
Also change some pointer arguments to references at some places where
0-pointers are not allowed.
llvm-svn: 192396
 | 
| | 
| 
| 
|  | 
llvm-svn: 192395
 | 
| | 
| 
| 
| 
| 
| 
|  | 
This makes the API a bit more natural to use and makes it easier to make
LiveRanges implementation details private.
llvm-svn: 192394
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
LiveRange just manages a list of segments and a list of value numbers
now as LiveInterval did previously, but without having details like spill
weight or a fixed register number.
LiveInterval is now a subclass of LiveRange and simply adds the spill weight
and the register number.
llvm-svn: 192393
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
The Segment struct contains a single interval; multiple instances of this struct
are used to construct a live range, but the struct is not a live range by
itself.
llvm-svn: 192392
 | 
| | 
| 
| 
|  | 
llvm-svn: 192391
 | 
| | 
| 
| 
|  | 
llvm-svn: 192386
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
DIScopeRef.
A paired commit at clang is required due to changes to DIBuilder.
llvm-svn: 192378
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
template_value are updated to use DIRef.
A paired commit at clang is required due to changes to DIBuilder.
llvm-svn: 192320
 | 
| | 
| 
| 
| 
| 
| 
|  | 
This fixes repeated -Wmicrosoft warnings when self-hosting clang on
Windows, and gets us real unsigned enum types with MSVC.
llvm-svn: 192227
 | 
| | 
| 
| 
|  | 
llvm-svn: 192218
 | 
| | 
| 
| 
|  | 
llvm-svn: 192216
 | 
| | 
| 
| 
|  | 
llvm-svn: 192215
 | 
| | 
| 
| 
|  | 
llvm-svn: 192199
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
This patch fixes an old FIXME by creating a MCTargetStreamer interface
and moving the target specific functions for ARM, Mips and PPC to it.
The ARM streamer is still declared in a common place because it is
used from lib/CodeGen/ARMException.cpp, but the Mips and PPC are
completely hidden in the corresponding Target directories.
I will send an email to llvmdev with instructions on how to use this.
llvm-svn: 192181
 | 
| | 
| 
| 
|  | 
llvm-svn: 192118
 | 
| | 
| 
| 
| 
| 
|  | 
assert got copy and pasted to many places.
llvm-svn: 192078
 | 
| | 
| 
| 
| 
| 
|  | 
This will be used to extend constructor aliases in clang.
llvm-svn: 192066
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
The most likely case where this error happens is when the user specifies
too many register operands. Don't make it look like an internal LLVM bug
when we can see that the error is coming from an inline asm instruction.
For other instructions we keep the "ran out of registers" error.
llvm-svn: 192041
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
When MC was first added, targets could use hasRawTextSupport to keep features
working before they were added to the MC interface.
The design goal of MC is to provide an uniform api for printing assembly and
object files. Short of relaxations and other corner cases, a object file is
just another representation of the assembly.
It was never the intention that targets would keep doing things like
if (hasRawTextSupport())
  Set flags in one way.
else
  Set flags in another way.
When they do that they create two code paths and the object file is no longer
just another representation of the assembly. This also then requires testing
with llc -filetype=obj, which is extremelly brittle.
This patch removes some of these hacks by replacing them with smaller ones.
The ARM flag setting is trivial, so I just moved it to the constructor. For
Mips, the patch adds two temporary hack directives that allow the assembly
to represent the same things as the object file was already able to.
The hope is that the mips developers will replace the hack directives with
the same ones that gas uses and drop the -print-hack-directives flag.
I will also try to implement a target streamer interface, so that we can
move this out of the common code.
In summary, for any new work, two rules of the thumb are
  * Don't use "llc -filetype=obj" in tests.
  * Don't add calls to hasRawTextSupport.
llvm-svn: 192035
 | 
| | 
| 
| 
| 
| 
|  | 
of MoveChild, CheckSame, MoveParent. Saves 846 bytes from the X86 DAG isel matcher, ~300 from ARM, ~840 from Hexagon.
llvm-svn: 192026
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
is updated to use DITypeRef.
Move isUnsignedDIType and getOriginalTypeSize from DebugInfo.h to be static
helper functions in DwarfCompileUnit. We already have a static helper function
"isTypeSigned" in DwarfCompileUnit, and a pointer to DwarfDebug is added to
resolve the derived-from field. All three functions need to go across link
for derived-from fields, so we need to get hold of a type identifier map.
A pointer to DwarfDebug is also added to DbgVariable in order to resolve the
derived-from field.
Debug info verifier is updated to check a derived-from field is a TypeRef.
Verifier will not go across link for derived-from fields, in debug info finder,
we go across the link to add derived-from fields to types.
Function getDICompositeType is only used by dragonegg and since dragonegg does
not generate identifier for types, we use an empty map to resolve the
derived-from field.
When printing a derived-from field, we use DITypeRef::getName to either return
the type identifier or getName of the DIType.
A paired commit at clang is required due to changes to DIBuilder.
llvm-svn: 192018
 | 
| | 
| 
| 
|  | 
llvm-svn: 192017
 | 
| | 
| 
| 
|  | 
llvm-svn: 192016
 | 
| | 
| 
| 
|  | 
llvm-svn: 192014
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
pointed to by a dbg_value belonging to a function argument is eliminated
during instruction selection.
rdar://problem/15094721.
llvm-svn: 192011
 | 
| | 
| 
| 
|  | 
llvm-svn: 192009
 | 
| | 
| 
| 
|  | 
llvm-svn: 192005
 | 
| | 
| 
| 
|  | 
llvm-svn: 192004
 | 
| | 
| 
| 
|  | 
llvm-svn: 192003
 | 
| | 
| 
| 
| 
| 
|  | 
scope, pass a scope.
llvm-svn: 192002
 | 
| | 
| 
| 
|  | 
llvm-svn: 192000
 | 
| | 
| 
| 
| 
| 
|  | 
* two actually due to some weird template thing... investigating that.
llvm-svn: 191998
 | 
| | 
| 
| 
|  | 
llvm-svn: 191994
 | 
| | 
| 
| 
| 
| 
|  | 
This has the side effect of using DW_FORM_flag_present on dwarf4 and above.
llvm-svn: 191991
 | 
| | 
| 
| 
| 
| 
|  | 
a flag. No functional change.
llvm-svn: 191990
 |