| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
Summary: Previously we would dereference Symtab without checking for null.
Reviewers: davide, atanasyan, rafael
Reviewed By: davide, atanasyan
Differential Revision: https://reviews.llvm.org/D38080
llvm-svn: 313970
|
| |
|
|
|
|
|
|
|
| |
This patch adds the -o and --out-file options for compatibility with
Darwin's dwarfdump.
Differential revision: https://reviews.llvm.org/D38125
llvm-svn: 313969
|
| |
|
|
|
|
| |
This is my test commit as it only changes two lines
llvm-svn: 313968
|
| |
|
|
| |
llvm-svn: 313967
|
| |
|
|
|
|
|
|
|
|
|
| |
Don't overwrite exit code in LSan when running on top of ASan in recovery mode
to avoid breakage of users code due to found leaks.
Patch by Slava Barinov.
Differential Revision: https://reviews.llvm.org/D38026
llvm-svn: 313966
|
| |
|
|
|
|
| |
This has since been removed.
llvm-svn: 313965
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D38163
llvm-svn: 313964
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This ignores case while sorting using-declarations, fixing a case where `_` would appear between lowercase and uppercase characters.
It also applies stable sort, so that replacements for the exact same using declarations are not generated.
Reviewers: klimek, alexfh
Reviewed By: alexfh
Subscribers: cfe-commits
Differential Revision: https://reviews.llvm.org/D37263
llvm-svn: 313963
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: A fix in documentation.
Reviewers: bkramer
Reviewed By: bkramer
Subscribers: JDevlieghere, xazax.hun
Differential Revision: https://reviews.llvm.org/D38087
llvm-svn: 313962
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds instruction patterns for operations in BPF_ALU. After this,
assembler could recognize some 32-bit ALU statement. For example, those listed
int the unit test file.
Separate MOV patterns are unnecessary as MOV is ALU operation that could reuse
ALU encoding infrastructure, this patch removed those redundant patterns.
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
Reviewed-by: Yonghong Song <yhs@fb.com>
llvm-svn: 313961
|
| |
|
|
|
|
|
| |
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
Reviewed-by: Yonghong Song <yhs@fb.com>
llvm-svn: 313960
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Arithmetic and jump instructions, load and store instructions are sharing
the same 8-bit code field encoding,
A better instruction pattern implemention could be the following inheritance
relationships, and each layer only encoding those fields which start to
diverse from that layer. This avoids some redundant code.
InstBPF -> TYPE_ALU_JMP -> ALU/JMP
InstBPF -> TYPE_LD_ST -> Load/Store
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
Reviewed-by: Yonghong Song <yhs@fb.com>
llvm-svn: 313959
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, eBPF backend is using some constant directly in instruction patterns,
This patch replace them with mnemonics and removed some unnecessary temparary
variables.
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
Reviewed-by: Yonghong Song <yhs@fb.com>
llvm-svn: 313958
|
| |
|
|
|
|
| |
purposes), so they never formally have linkage.
llvm-svn: 313957
|
| |
|
|
|
|
|
|
|
| |
The previous SwiftCC support for AAPCS64 was partially correct. It
setup swiftself parameters in the proper register but failed to setup
swifterror in the correct register. This would break compilation of
swift code for non-Darwin AAPCS64 conforming environments.
llvm-svn: 313956
|
| |
|
|
|
|
|
|
|
|
|
| |
variable templates.
This implements the proposed approach in https://github.com/itanium-cxx-abi/cxx-abi/issues/33
This reinstates r313827, reverted in r313856, with a fix for the 'out-of-bounds
enumeration value' ubsan error in that change.
llvm-svn: 313955
|
| |
|
|
|
|
|
| |
This code path is entirely untested and not really maintained. The
expected use here is with libc++ only.
llvm-svn: 313954
|
| |
|
|
| |
llvm-svn: 313953
|
| |
|
|
| |
llvm-svn: 313952
|
| |
|
|
| |
llvm-svn: 313951
|
| |
|
|
|
|
|
|
| |
The script updates reference results from the previous run, and stages them.
Differential Revision: https://reviews.llvm.org/D38157
llvm-svn: 313950
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Exporting needed function for future reuse.
- Idiomatic python: using with `file as f` instead of `try/finally`.
- Fixing some indentation issues.
- No need to reinvent python `multiprocessing.getCPUCount()`
- Removing a function parameter which is always the same under all invocations.
- Adding some docstrings.
Differential Revision: https://reviews.llvm.org/D38156
llvm-svn: 313949
|
| |
|
|
|
|
|
|
|
|
| |
I've been unable to find any cases whose behavior is actually changed by this,
but only because an implicitly deleted destructor also results in it being
impossible to have a trivial (non-deleted) copy constructor, which the place
where this really matters (choosing whether to pass a class in registers)
happens to also check.
llvm-svn: 313948
|
| |
|
|
|
|
| |
[-Wunused-function]
llvm-svn: 313947
|
| |
|
|
| |
llvm-svn: 313946
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The attribute informs the compiler that the annotated pointer parameter
of a function cannot escape and enables IRGen to attach attribute
'nocapture' to parameters that are annotated with the attribute. That is
the only optimization that currently takes advantage of 'noescape', but
there are other optimizations that will be added later that improves
IRGen for ObjC blocks.
This recommits r313722, which was reverted in r313725 because clang
couldn't build compiler-rt. It failed to build because there were
function declarations that were missing 'noescape'. That has been fixed
in r313929.
rdar://problem/19886775
Differential Revision: https://reviews.llvm.org/D32210
llvm-svn: 313945
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D37910
llvm-svn: 313944
|
| |
|
|
| |
llvm-svn: 313943
|
| |
|
|
|
|
|
| |
Move function call into debug macro to suppress unused variable warning
in non-debug builds.
llvm-svn: 313942
|
| |
|
|
|
|
| |
You Use warnings; other minor fixes (NFC).
llvm-svn: 313941
|
| |
|
|
| |
llvm-svn: 313940
|
| |
|
|
| |
llvm-svn: 313939
|
| |
|
|
| |
llvm-svn: 313938
|
| |
|
|
|
|
| |
This found one place in lld that was not checking the error.
llvm-svn: 313937
|
| |
|
|
| |
llvm-svn: 313936
|
| |
|
|
| |
llvm-svn: 313935
|
| |
|
|
|
|
|
|
|
| |
changes going
in today and don't want the two changes to confuse the situation with the build bots.
I'll commit tomorrow once they're known good.
llvm-svn: 313934
|
| |
|
|
| |
llvm-svn: 313933
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
devices.
Normal customer devices won't be able to run these devices, we're hoping to get
a public facing bot set up at some point.
There will be some smaller follow-on patches. The changes to tools/lldb-server are
verbose and I'm not thrilled with having to skip all of these tests manually.
There are a few places where I'm making the assumption that "armv7", "armv7k", "arm64"
means it's an ios device, and I need to review & clean these up with an OS check
as well. (Android will show up as "arm" and "aarch64" so by pure luck they shouldn't
cause problems, but it's not an assumption I want to rely on).
I'll be watching the bots for the rest of today; if any problems are introduced by
this patch I'll revert it - if anyone sees a problem with their bot that I don't
see, please do the same. I know it's a rather large patch.
One change I had to make specifically for iOS devices was that debugserver can't
create files. There were several tests that launch the inferior process redirecting
its output to a file, then they retrieve the file. They were not trying to test
file redirection in these tests, so I rewrote those to write their output to a file
directly.
llvm-svn: 313932
|
| |
|
|
|
|
|
|
|
|
| |
HexagonVectorLoopCarriedReuse pass"
This reverts commit r313926.
It was failing in some bots.
llvm-svn: 313931
|
| |
|
|
| |
llvm-svn: 313930
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit annotates the block parameters of the following functions
declared in compiler-rt with 'noescape':
- dispatch_sync
- dispatch_barrier_sync
- dispatch_once
- dispatch_apply
This is needed to commit the patch that adds support for 'noescape' in
clang (see https://reviews.llvm.org/D32210) since these functions are
annotated with 'noescape' in the SDK header files.
Differential Revision: https://reviews.llvm.org/D32210
llvm-svn: 313929
|
| |
|
|
|
|
|
|
| |
There were two issues, one Python 3 specific related to Unicode,
and another which is that the tool substitution for lld no longer
rejected matches where a / preceded the tool name.
llvm-svn: 313928
|
| |
|
|
|
|
|
|
|
| |
This change is required to easily test the given checkout of the analyzer,
rather than the one bundled with a system compiler.
Differential Revision: https://reviews.llvm.org/D38155
llvm-svn: 313927
|
| |
|
|
|
|
| |
added HexagonVectorLoopCarriedReuse pass
llvm-svn: 313926
|
| |
|
|
|
|
|
|
|
|
| |
This patch adds a pass that removes the computation of provably redundant
expressions that have been computed earlier in a previous iteration. It
relies on the use of PHIs to identify loop carried dependences.
This is scalar replacement for vector types.
llvm-svn: 313925
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D38003
llvm-svn: 313924
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D38003
llvm-svn: 313923
|
| |
|
|
|
|
|
|
| |
This is breaking several bots. I have enough information to
investigate, so I'm reverting to green until I get it figured
out.
llvm-svn: 313922
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the second slice of a Mach-O universal file.
The code in llvm-objdump in in DisassembleMachO() was getting the default
CPU then incorrectly setting into the global variable used for the -mcpu option
if that was not set. This caused a second call to DisassembleMachO() to use
the wrong default CPU when disassembling the next slice in a Mach-O universal
file. And would result in bad disassembly and an error message about an
recognized processor for the target:
% llvm-objdump -d -m -arch all fat.macho-armv7s-arm64
fat.macho-armv7s-arm64 (architecture armv7s):
(__TEXT,__text) section
armv7:
0: 60 47 bx r12
fat.macho-armv7s-arm64 (architecture arm64):
'cortex-a7' is not a recognized processor for this target (ignoring processor)
'cortex-a7' is not a recognized processor for this target (ignoring processor)
(__TEXT,__text) section
___multc3:
0: .long 0x1e620810
rdar://34439149
llvm-svn: 313921
|