| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 193433
|
| |
|
|
| |
llvm-svn: 193432
|
| |
|
|
| |
llvm-svn: 193431
|
| |
|
|
|
|
|
| |
GCC on fedora 18 ARM only uses 2 -L options. Clang prints two extra ones, but
we should not include them in the test as they are not required.
llvm-svn: 193430
|
| |
|
|
| |
llvm-svn: 193429
|
| |
|
|
|
|
| |
clang first so that the build still works.
llvm-svn: 193428
|
| |
|
|
| |
llvm-svn: 193427
|
| |
|
|
| |
llvm-svn: 193426
|
| |
|
|
|
|
|
|
| |
Added a new key that we understand for the "qHostInfo" packet: "default_packet_timeout:T;" where T is a default packet timeout in seconds.
This allows GDB servers with known slow packet response times to increase the default timeout to a value that makes sense for the connection.
llvm-svn: 193425
|
| |
|
|
| |
llvm-svn: 193424
|
| |
|
|
|
|
|
| |
We don't have any checks that depend on the version of fedora, so we can
simplify.
llvm-svn: 193423
|
| |
|
|
|
|
|
|
| |
vbroadcast intrinsics.
Patch by Cameron McInally <cameron.mcinally@nyu.edu>
llvm-svn: 193422
|
| |
|
|
|
|
|
|
| |
intrinsics.
Patch by Cameron McInally <cameron.mcinally@nyu.edu>
llvm-svn: 193421
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Currently shared library builds (BUILD_SHARED_LIBS=ON in cmake) fail three
bugpoint tests (BugPoint/remove_arguments_test.ll,
BugPoint/crash-narrowfunctiontest.ll, and BugPoint/metadata.ll).
If I run the bugpoint commands that llvm-lit runs with without -silence-passes
I see errors such as this:
opt: error while loading shared libraries: libLLVMSystemZInfo.so: failed to
map segment from shared object: Cannot allocate memory
It seems that the increased size of the binaries in a shared library build is
causing the subprocess to exceed the 100MB memory limit. This patch therefore
increases the default limit to a level at which these tests pass.
Reviewers: dsanders
Reviewed By: dsanders
CC: llvm-commits, rafael
Differential Revision: http://llvm-reviews.chandlerc.com/D2013
llvm-svn: 193420
|
| |
|
|
| |
llvm-svn: 193419
|
| |
|
|
|
|
|
|
|
|
|
| |
Specifically, this warns when a character literal is added (using '+') to a
variable with type 'char *' (or any other pointer to character type). Like
-Wstring-plus-int, there is a fix-it to change "foo + 'a'" to "&foo['a']"
iff the character literal is on the right side of the string.
Patch by Anders Rönnholm!
llvm-svn: 193418
|
| |
|
|
| |
llvm-svn: 193417
|
| |
|
|
|
|
| |
Detected by valgrind.
llvm-svn: 193416
|
| |
|
|
| |
llvm-svn: 193415
|
| |
|
|
| |
llvm-svn: 193414
|
| |
|
|
| |
llvm-svn: 193413
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fix a memory leak found by valgrind.
Calling it from the base class destructor would not destroy the BasicCallGraph
bits.
FIXME: BasicCallGraph is the only thing that inherits from CallGraph. Can
we merge the two?
llvm-svn: 193412
|
| |
|
|
|
|
|
|
|
|
|
|
| |
hybrid mode only.
When running application in DynamoRIO hybrid mode only, only uninstrumented
modules will run in DynamoRIO and be instrumented by the client, so we do not
need module table in MSanDR.
Patch by Qin Zhao.
llvm-svn: 193411
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically make clang-format less eager to break after the opening
parenthesis of a function call.
Before:
aaaaaaaaaaaaaaaaa(
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa + aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa);
After:
aaaaaaaaaaaaaaaaa(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa +
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa);
Apparently that is preferable. This penalties are adapted
conservatively, we might have to increase them a little bit further.
llvm-svn: 193410
|
| |
|
|
|
|
| |
The function is deprecated.
llvm-svn: 193409
|
| |
|
|
| |
llvm-svn: 193408
|
| |
|
|
| |
llvm-svn: 193407
|
| |
|
|
| |
llvm-svn: 193406
|
| |
|
|
| |
llvm-svn: 193405
|
| |
|
|
| |
llvm-svn: 193404
|
| |
|
|
|
|
|
|
|
|
| |
When assembling, a .thumb_func directive is supposed to be applicable to the
next symbol definition, even if there are intervening directives. We were
racing ahead to try and find it, and this commit should fix the issue.
Patch by Gabor Ballabas
llvm-svn: 193403
|
| |
|
|
| |
llvm-svn: 193402
|
| |
|
|
|
|
| |
whiteline.
llvm-svn: 193401
|
| |
|
|
|
|
|
|
| |
some tests test libc/filesystem error handling paths (e.g. close(INT_MAX)),
currently such tests fail
with this change they work as expected
llvm-svn: 193400
|
| |
|
|
|
|
|
|
|
|
| |
There's a barrier instruction so that should still be used, but most actual
atomic operations are going to need a platform decision on the correct
behaviour (either nop if single-threaded or OS-support otherwise).
rdar://problem/15287210
llvm-svn: 193399
|
| |
|
|
|
|
|
|
|
|
|
| |
ARM processors without ldrex/strex need to be able to make libcalls for all
atomic operations, including the newer min/max versions.
The alternative would probably be expanding these operations in terms of
cmpxchg (as x86 does always), but in the configurations where this matters
code-size tends to be paramount so the libcall is more desirable.
llvm-svn: 193398
|
| |
|
|
|
|
|
|
|
| |
We would previously not diagnose this which would lead to crashes (on
very strange code).
This fixes PR17675.
llvm-svn: 193397
|
| |
|
|
| |
llvm-svn: 193396
|
| |
|
|
| |
llvm-svn: 193395
|
| |
|
|
|
|
|
| |
A TableGen indeterminacy means that the reason for the failure can
vary, and Windows gets the other option.
llvm-svn: 193394
|
| |
|
|
|
|
|
| |
This optimization is not SSE specific so I am moving it to DAGco.
The new scalar_to_vector dag node exposed a missing pattern in the AArch64 target that I needed to add.
llvm-svn: 193393
|
| |
|
|
|
|
|
|
|
| |
__ARM_ARCH_EXT_IDIV__ is the define that ARM is using to indicate the presence
of hardware integer divide (sdiv/udiv). Previously, this code was only being
invoked for processors marked 7S. We now can correctly generate hardware
divides on cortex-a15 devices.
llvm-svn: 193392
|
| |
|
|
| |
llvm-svn: 193391
|
| |
|
|
| |
llvm-svn: 193390
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
llvm-cov will now be able to read program counts from the GCDA file and
output it in the same format as gcov. The program summary tag was
identified from gcov-io.h as "\0\0\0\a3".
There is currently a bug in GCOVProfiling.cpp which does not generate
the
run- or program-counting IR, so this change was tested manually by
modifying the GCDA file and comparing the gcov and llvm-cov outputs.
llvm-svn: 193389
|
| |
|
|
|
|
| |
Without this patch we would warn and fail to output the function in the test.
llvm-svn: 193388
|
| |
|
|
| |
llvm-svn: 193387
|
| |
|
|
|
|
|
|
|
|
|
| |
Change the uninitialized field warnings so that field initializers are checked
inside the constructor. Previously, in class initializers were checked
separately. Running one set of checks also simplifies the logic for preventing
duplicate warnings. Added new checks to warn when an uninitialized field is
used in base class initialization. Also fixed misspelling of uninitialized
and moved all code for this warning together.
llvm-svn: 193386
|
| |
|
|
| |
llvm-svn: 193385
|
| |
|
|
| |
llvm-svn: 193384
|