| Commit message (Collapse) | Author | Age | Files | Lines | 
| ... |  | 
| | 
| 
| 
|  | 
llvm-svn: 204357
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
The Octeon cpu from Cavium Networks is mips64r2 based and has an extended
instruction set. In order to utilize this with LLVM, a new cpu feature "octeon"
and a subtarget feature "cnmips" is added. A small set of new instructions
(baddu, dmul, pop, dpop, seq, sne) is also added. LLVM generates dmul, pop and
dpop instructions with option -mcpu=octeon or -mattr=+cnmips.
llvm-svn: 204337
 | 
| | 
| 
| 
| 
| 
|  | 
Fixes https://code.google.com/p/address-sanitizer/issues/detail?id=279.
llvm-svn: 204331
 | 
| | 
| 
| 
|  | 
llvm-svn: 204329
 | 
| | 
| 
| 
| 
| 
|  | 
Differential Revision: http://llvm-reviews.chandlerc.com/D3112
llvm-svn: 204325
 | 
| | 
| 
| 
| 
| 
|  | 
http://llvm-reviews.chandlerc.com/D3080
llvm-svn: 204323
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
Also removed some unnecessary #includes.
No functional changes.
llvm-svn: 204320
 | 
| | 
| 
| 
|  | 
llvm-svn: 204318
 | 
| | 
| 
| 
| 
| 
| 
|  | 
We would emit a pair of double quotes inside a pair of single quotes.
Just use a pair of single quotes.
llvm-svn: 204312
 | 
| | 
| 
| 
| 
| 
| 
|  | 
Re-apply the change after it was reverted to do conflicts due to another change
being reverted.
llvm-svn: 204306
 | 
| | 
| 
| 
| 
| 
|  | 
particular this makes a too short instruction with a missing SIB byte fail.
llvm-svn: 204305
 | 
| | 
| 
| 
| 
| 
|  | 
treating DPair as QPR.
llvm-svn: 204304
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Given
bar = foo + 4
	.long bar
MC would eat the 4. GNU as includes it in the relocation. The rule seems to be
that a variable that defines a symbol is used in the relocation and one that
does not define a symbol is evaluated and the result included in the relocation.
Fixing this unfortunately required some other changes:
* Since the variable is now evaluated, it would prevent the ELF writer from
  noticing the weakref marker the elf streamer uses. This patch then replaces
  that with a VariantKind in MCSymbolRefExpr.
* Using VariantKind then requires us to look past other VariantKind to see
	.weakref	bar,foo
	call	bar@PLT
  doing this also fixes
	zed = foo +2
	call zed@PLT
  so that is a good thing.
* Looking past VariantKind means that the relocation selection has to use
  the fixup instead of the target.
This is a reboot of the previous fixes for MC. I will watch the sanitizer
buildbot and wait for a build before adding back the previous fixes.
llvm-svn: 204294
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
This appears to trigger failures with optimization and function arguments somehow.
This reverts commit r204277.
llvm-svn: 204286
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
This commit moves us from a single range per subprogram to extending
ranges if we are:
a) In the same section, and
b) In the same enclosing CU.
This means we have more fine grained ranges for compile units, and fewer
ranges overall when we have multiple functions in the same CU
adjacent to each other in the object file.
Also remove all of the earlier hacks around this functionality for
function sections etc. Also update all of the testcases to take into
account the merging functionality.
llvm-svn: 204277
 | 
| | 
| 
| 
|  | 
llvm-svn: 204275
 | 
| | 
| 
| 
|  | 
llvm-svn: 204274
 | 
| | 
| 
| 
| 
| 
| 
|  | 
v2:
  -Use correct opcode for DS_READ_64
llvm-svn: 204273
 | 
| | 
| 
| 
|  | 
llvm-svn: 204272
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
It isn't actually used now, and probably never will be, plus it makes
tests less annoying. I also think SC prints GDS instructions as a
separate instruction name.
llvm-svn: 204270
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
Also remove unused data fields from the DS_Load_Helper class.
v2:
  - Merge fields for DS_WRITE
llvm-svn: 204269
 | 
| | 
| 
| 
|  | 
llvm-svn: 204256
 | 
| | 
| 
| 
|  | 
llvm-svn: 204252
 | 
| | 
| 
| 
|  | 
llvm-svn: 204230
 | 
| | 
| 
| 
|  | 
llvm-svn: 204216
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
The current state of affairs has auxiliary symbols described as a big
bag of bytes. This is less than satisfying, it detracts from the YAML
file as being human readable.
Instead, allow for symbols to optionally contain their auxiliary data.
This allows us to have a much higher level way of describing things like
weak symbols, function definitions and section definitions.
This depends on D3105.
Differential Revision: http://llvm-reviews.chandlerc.com/D3092
llvm-svn: 204214
 | 
| | 
| 
| 
| 
| 
|  | 
This reverts commit r204178.
llvm-svn: 204203
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
debug_line.dwo
This isn't a complete fix - it falls back to non-comp_dir when multiple
compile units are in play. Adding a map of comp_dir to table is part of
the more general solution, but I gave up (in the short term) when I
realized I'd also have to calculate the size of each type unit so as to
produce correct DW_AT_stmt_list attributes.
llvm-svn: 204202
 | 
| | 
| 
| 
| 
| 
|  | 
Differential Revision: http://llvm-reviews.chandlerc.com/D3103
llvm-svn: 204199
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
The use_iterator redesign in r203364 introduced an increment past the
end of a range in -objc-arc-contract.  Added an explicit check for the
end of the range.
<rdar://problem/16333235>
llvm-svn: 204195
 | 
| | 
| 
| 
| 
| 
|  | 
No functional change.
llvm-svn: 204192
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
When deployment target version information is available, emit it to the
target streamer for inclusion in the object file.
rdar://11337778
llvm-svn: 204191
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Allow object files to be tagged with a version-min load command for iOS
or MacOSX.
Teach macho-dump to understand the version-min load commands for
testcases.
rdar://11337778
llvm-svn: 204190
 | 
| | 
| 
| 
| 
| 
|  | 
for this kind of walk.
llvm-svn: 204188
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
noise.
Original commit log:
Replace some dead code with an assert. When I first ported this pass
from a loop pass to a function pass I did so in the naive, recursive
way. It doesn't actually work, we need a worklist instead. When
I switched to the worklist I didn't delete the naive recursion. That
recursion was also buggy because it was dead and never really exercised.
llvm-svn: 204187
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
pass from a loop pass to a function pass I did so in the naive,
recursive way. It doesn't actually work, we need a worklist instead.
When I switched to the worklist I didn't delete the naive recursion.
That recursion was also buggy because it was dead and never really
exercised.
llvm-svn: 204184
 | 
| | 
| 
| 
|  | 
llvm-svn: 204183
 | 
| | 
| 
| 
| 
| 
|  | 
We really do use these things in the header.
llvm-svn: 204180
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
This reverts commit r204137.
This includes a fix for handling aliases of aliases.
llvm-svn: 204178
 | 
| | 
| 
| 
|  | 
llvm-svn: 204177
 | 
| | 
| 
| 
|  | 
llvm-svn: 204176
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
For functions where esi is used as base pointer, we would previously fall back
from lowering memcpy with "rep movs" because that clobbers esi.
With this patch, we just store esi in another physical register, and restore
it afterwards. This adds a little bit of register preassure, but the more
efficient memcpy should be worth it.
Differential Revision: http://llvm-reviews.chandlerc.com/D2968
llvm-svn: 204174
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Summary:
  SLP Vectorization of intrinsics (r203707) has exposed cases where the
  expansion of vector bswap is failing (PR19151).
Reviewers: hfinkel
CC: chandlerc
Differential Revision: http://llvm-reviews.chandlerc.com/D3104
llvm-svn: 204163
 | 
| | 
| 
| 
| 
| 
|  | 
Follow-up to r203982.
llvm-svn: 204162
 | 
| | 
| 
| 
|  | 
llvm-svn: 204161
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
following rules:
 1)  (AND (shuf (A, C, Mask), shuf (B, C, Mask)) -> shuf (AND (A, B), C, Mask)
 2)  (OR  (shuf (A, C, Mask), shuf (B, C, Mask)) -> shuf (OR  (A, B), C, Mask)
 3)  (XOR (shuf (A, C, Mask), shuf (B, C, Mask)) -> shuf (XOR (A, B), V_0, Mask)
 4)  (AND (shuf (C, A, Mask), shuf (C, B, Mask)) -> shuf (C, AND (A, B), Mask)
 5)  (OR  (shuf (C, A, Mask), shuf (C, B, Mask)) -> shuf (C, OR  (A, B), Mask)
 6)  (XOR (shuf (C, A, Mask), shuf (C, B, Mask)) -> shuf (V_0, XOR (A, B), Mask)
llvm-svn: 204160
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Summary:
X86BaseInfo.h defines an enum for the offset of each operand in a memory operand
sequence.  Some code uses it and some does not.  This patch replaces (hopefully)
all remaining locations where an integer literal was used instead of this enum.
No functionality change intended.
Reviewers: nadav
CC: llvm-commits, t.p.northover
Differential Revision: http://llvm-reviews.chandlerc.com/D3108
llvm-svn: 204158
 | 
| | 
| 
| 
|  | 
llvm-svn: 204157
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
When converting a signed 32-bit integer to double-precision floating point on
hardware without a lfiwax instruction, we have to instead use a lfd followed
by fcfid.  We were erroneously offsetting the address by 4 bytes in
preparation for either a lfiwax or lfiwzx when generating the lfd.  This fixes
that silly error.
This was not caught in the test suite since the conversion tests were run with
-mcpu=pwr7, which implies availability of lfiwax.  I've added another test
case for older hardware that checks the code we expect in the absence of
lfiwax and other flavors of fcfid.  There are fewer tests in this test case
because we punt to DAG selection in more cases on older hardware.  (We must
generate complex fiddly sequences in those cases, and there is marginal
benefit in duplicating that logic in fast-isel.)
llvm-svn: 204155
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
LLVM part of MSan implementation of advanced origin tracking,
when we record not only creation point, but all locations where
an uninitialized value was stored to memory, too.
llvm-svn: 204151
 |