| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 196908
|
|
|
|
| |
llvm-svn: 196907
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One unusual feature of the z architecture is that the result of a
previous load can be reused indefinitely for subsequent loads, even if
a cache-coherent store to that location is performed by another CPU.
A special serializing instruction must be used if you want to force
a load to be reattempted.
Since volatile loads are not supposed to be omitted in this way,
we should insert a serializing instruction before each such load.
The same goes for atomic loads.
The patch implements this at the IR->DAG boundary, in a similar way
to atomic fences. It is a no-op for targets other than SystemZ.
llvm-svn: 196906
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One unusual feature of the z architecture is that the result of a
previous load can be reused indefinitely for subsequent loads, even if
a cache-coherent store to that location is performed by another CPU.
A special serializing instruction must be used if you want to force
a load to be reattempted.
Since volatile loads are not supposed to be omitted in this way,
we should insert a serializing instruction before each such load.
The same goes for atomic loads.
The patch implements this at the IR->DAG boundary, in a similar way
to atomic fences. It is a no-op for targets other than SystemZ.
llvm-svn: 196905
|
|
|
|
|
|
| |
It depends on nothing described in LLVM_LINK_COMPONENTS.
llvm-svn: 196902
|
|
|
|
|
|
| |
This is a small change to be strict. Just want get pattern safer.
llvm-svn: 196889
|
|
|
|
| |
llvm-svn: 196887
|
|
|
|
| |
llvm-svn: 196882
|
|
|
|
|
|
| |
I'll prune redundant deps in LLVMBuild.txt, later.
llvm-svn: 196881
|
|
|
|
| |
llvm-svn: 196880
|
|
|
|
|
|
|
| |
This reverts commit r196876. Its tests failed on the bots, so I'll
figure it out tomorrow.
llvm-svn: 196879
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For stack frames requiring realignment, three pointers may be needed:
- ebp to address incoming arguments
- esi (could be any callee-saved register) to address locals
- esp to address outgoing arguments
We would use esi unconditionally without verifying that it did not
conflict with inline assembly.
This change doesn't do the verification, it simply emits a fatal error
on functions that use stack realignment, dynamic SP adjustments, and
inline assembly.
Because stack realignment is common on Windows, we also no longer assume
that MS inline assembly clobbers esp. Instead, we analyze the inline
instructions for implicit definitions and check if esp is there. If so,
we require the use of a base pointer and consider it in the condition
above.
Mostly fixes PR16830, but we could try harder to find a non-conflicting
base pointer.
Reviewers: sunfish
Differential Revision: http://llvm-reviews.chandlerc.com/D1317
llvm-svn: 196876
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MCJIT needs to be able to run in hostile environments, even when PWD
is invalid. There's no need to crash MCJIT in this case.
The obvious fix is to simply leave MCContext's CompilationDir empty
when PWD can't be determined. This way, MCJIT clients,
and other clients that link with LLVM don’t need a valid working directory.
If we do want to guarantee valid CompilationDir, that should be done
only for clients of getCompilationDir(). This is as simple as checking
for an empty string.
The only current use of getCompilationDir is EmitGenDwarfInfo, which
won’t conceivably run with an invalid working dir. However, in the
purely hypothetically and untestable case that this happens, the
AT_comp_dir will be omitted from the compilation_unit DIE.
llvm-svn: 196874
|
|
|
|
| |
llvm-svn: 196873
|
|
|
|
| |
llvm-svn: 196858
|
|
|
|
| |
llvm-svn: 196857
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to gcov, llvm-cov will now print out the block count at the end
of each block. Multiple blocks can end on the same line.
One computational difference is by using -a, llvm-cov will no longer
simply add the block counts together to form a line count. Instead, it
will take the maximum of the block counts on that line. This has a
similar effect to what gcov does, but generates more correct counts in
certain scenarios.
Also updated tests.
llvm-svn: 196856
|
|
|
|
| |
llvm-svn: 196851
|
|
|
|
| |
llvm-svn: 196850
|
|
|
|
|
|
| |
empty one.
llvm-svn: 196849
|
|
|
|
| |
llvm-svn: 196848
|
|
|
|
|
|
| |
Thanks to Jim Grosbach for noticing it.
llvm-svn: 196846
|
|
|
|
|
|
|
|
| |
This avoids creating branch weight metadata of length one when we fold
cases into the default of a switch instruction, which was triggering
an assert.
llvm-svn: 196845
|
|
|
|
|
|
| |
clarity. No functional change.
llvm-svn: 196844
|
|
|
|
| |
llvm-svn: 196843
|
|
|
|
|
|
| |
ambiguous. Reformat to match.
llvm-svn: 196838
|
|
|
|
|
|
| |
float/double rather than the vector equivalents when appropriate.
llvm-svn: 196833
|
|
|
|
|
|
| |
unnecessary patterns in tablegen.
llvm-svn: 196832
|
|
|
|
|
|
| |
pairwise implementation, using an overloaded definition instead.
llvm-svn: 196831
|
|
|
|
| |
llvm-svn: 196829
|
|
|
|
|
|
| |
This is part of the mips16 epilogue/prologue cleanup.
llvm-svn: 196824
|
|
|
|
|
|
| |
This matches the behavior of both msvc and mingw.
llvm-svn: 196814
|
|
|
|
|
|
| |
No functionality change.
llvm-svn: 196811
|
|
|
|
| |
llvm-svn: 196807
|
|
|
|
|
|
|
|
|
|
|
| |
Patch by Jiangning Liu.
With some test case changes:
- intrinsic test added to the existing /test/CodeGen/AArch64/neon-aba-abd.ll.
- New test cases to cover movi 1D scenario without using the intrinsic in
test/CodeGen/AArch64/neon-mov.ll.
llvm-svn: 196806
|
|
|
|
|
|
| |
gnu_ranges label in the unit.
llvm-svn: 196793
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
When clang is used under GNU/Linux in a chroot without /proc mount, it falls
back on the BSD method. However, since the buf variable is used twice
and fails with snprintf to produce the correct path.
When called as relatived (ie ./clang), it was failing with:
"" -cc1 [...] -x c++ x.cc
error: unable to execute command: Executable "" doesn't exist!
I also took the opportunity to simply the code (the first arg of test_dir
was useless).
Reviewers: rafael
Reviewed By: rafael
CC: cfe-commits
Differential Revision: http://llvm-reviews.chandlerc.com/D2361
llvm-svn: 196791
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unaligned offsets.
Summary:
The MSA ld.[bhwd] and st.[bhwd] instructions scale the immediate by the
element size before use as an offset. The offset must therefore be a
multiple of the element size to be valid in these instructions. However,
an unaligned base address is valid in MSA.
This commit causes the compiler to emit valid code when the calculated
offset is not a multiple of the element size by accounting for the offset
using addiu and using a zero offset in the load/store.
Depends on D2338
Reviewers: matheusalmeida
Reviewed By: matheusalmeida
Differential Revision: http://llvm-reviews.chandlerc.com/D2339
llvm-svn: 196777
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
The immediate in these instructions is scaled before use as an offset.
They therefore have a wider reach than ld.b/st.b.
Reviewers: matheusalmeida
Reviewed By: matheusalmeida
Differential Revision: http://llvm-reviews.chandlerc.com/D2338
llvm-svn: 196775
|
|
|
|
|
|
|
|
|
| |
the parsing is directed to set alias for register. This will result in errors reported when expressions containing label references are parsed(for example long jumps)
As we can't make a complete solution now it has been decided to enable .set directive to handle long jump expressions. This will cause parser to report errors when parsing integer based register assignments, for example:
.set r3, will be reported as error. Still, the need for expressions is higher priority as the integer based register assignments are Mips specific and can be avoided using register names.
llvm-svn: 196773
|
|
|
|
|
|
|
| |
This adds rbegin/rend methods to MutableArrayRef, they will be used by a
follow-on commit in clang.
llvm-svn: 196768
|
|
|
|
|
|
| |
BIAS on sparcV9.
llvm-svn: 196755
|
|
|
|
|
|
| |
umulo/smulo can be lowered on sparcv9 without an assertion error.
llvm-svn: 196751
|
|
|
|
|
|
|
| |
int32_t vminv_s32(int32x2_t a)
which should be compiled into SMINP Vd.2S,Vn.2S,Vm.2S
llvm-svn: 196749
|
|
|
|
| |
llvm-svn: 196748
|
|
|
|
|
|
| |
This fixes PR18150.
llvm-svn: 196735
|
|
|
|
| |
llvm-svn: 196732
|
|
|
|
|
|
| |
in the td file.
llvm-svn: 196731
|
|
|
|
|
|
| |
here is to make save/restore into variable number of argument instructions.
llvm-svn: 196726
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When trying to eliminate an "sub sp, sp, #N" instruction by folding
it into an existing push/pop using dummy registers, we need to account
for the fact that this might affect precisely how "fp" gets set in the
prologue.
We were attempting this, but assuming that *whenever* we performed a
fold it would make a difference. This is false, for example, in:
push {r4, r7, lr}
add fp, sp, #4
vpush {d8}
sub sp, sp, #8
we can fold the "sub" into the "vpush", forming "vpush {d7, d8}".
However, in that case the "add fp" instruction mustn't change, which
we were getting wrong before.
Should fix PR18160.
llvm-svn: 196725
|