| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Failure: undefined symbol 'Lline_table_start0'.
Root-cause: we use a symbol subtraction to calculate at_stmt_list, but
the line table entries are not dumped in the assembly.
Fix: use zero instead of a symbol subtraction for Compile Unit 0.
llvm-svn: 174479
|
| |
|
|
|
|
|
| |
- As of this commit, the test suite should now fully pass on both darwin11 and
darwin12 when testing against either a locally built libc++ or the system libc++.
llvm-svn: 174478
|
| |
|
|
|
|
| |
rdar://13153516
llvm-svn: 174477
|
| |
|
|
|
|
| |
The first part of the fix for having LLDB handle LTO debugging when the DWARF is in the .o files. This part separates the object file's modules into a separate cache map that maps unique C strings for the N_OSO path to the ModuleSP since one object file might be mentioned more than once in LTO binaries.
llvm-svn: 174476
|
| |
|
|
|
|
|
| |
- The trickery can confuse more basic source processors, in particular the
Unix conformance tool that wants to scan headers.
llvm-svn: 174475
|
| |
|
|
|
|
| |
"list" alias which has now been turned into a regex command that mimics the GDB equivalent. Changed "list" to "source list" to get around this problem.
llvm-svn: 174474
|
| |
|
|
| |
llvm-svn: 174473
|
| |
|
|
|
|
|
|
| |
ObjC++ alongside ObjC.
\end paranoia.
llvm-svn: 174471
|
| |
|
|
|
|
|
| |
- Otherwise, we never were actually linking against the right library when
building the test applications.
llvm-svn: 174470
|
| |
|
|
| |
llvm-svn: 174469
|
| |
|
|
|
|
|
|
|
|
|
| |
This is a "quick fix".
The underlining issue is that when a const pointer to a struct is passed
into a function, we do not invalidate the pointer fields. This results
in false positives that are common in C++ (since copy constructors are
prevalent). (Silences two llvm false positives.)
llvm-svn: 174468
|
| |
|
|
|
|
| |
AttributeSet.
llvm-svn: 174467
|
| |
|
|
| |
llvm-svn: 174466
|
| |
|
|
| |
llvm-svn: 174465
|
| |
|
|
| |
llvm-svn: 174464
|
| |
|
|
| |
llvm-svn: 174463
|
| |
|
|
|
|
| |
a setter and fix some comments.
llvm-svn: 174462
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
SELECTOR_REFERENCES in both the fragile and non-fragile API.
This is to ensure that GlobalOpt in LLVM does not attempt to look through a
selector reference to a method var name at compile time.
I also added a test/updated old tests that need to recognize the new keyword.
rdar://12580965.
llvm-svn: 174461
|
| |
|
|
|
|
|
|
|
|
| |
If an Apple llvmCore build is done without assertions, and a client uses
the llvmCore headers with assertions enabled, or vice versa, then things will
break because some of the structure sizes in the API are different. Use the
unifdef tool to make the headers unconditionally match the way the llvmCore
libraries were built.
llvm-svn: 174460
|
| |
|
|
| |
llvm-svn: 174459
|
| |
|
|
|
|
|
|
|
| |
This reverts commit a33e1fafac7fedb1b080ef07ddf9ad6ddff3a830.
This unit test crashes on Darwon. It needs to be temporarily reverted
to unblock the test infrastructure.
llvm-svn: 174458
|
| |
|
|
|
|
|
|
| |
The stuff we're handing are all enums (Attribute::AttrKind), integers and
strings. Don't convert them to Constants, which is an unnecessary step here. The
rest of the changes are mostly mechanical.
llvm-svn: 174456
|
| |
|
|
|
|
|
|
|
| |
function stub routine addresses from an in-memory-only
MachO object file. This was the only remaining part of
ParseSymtab() that was assuming a file exists.
<rdar://problem/13139585>
llvm-svn: 174455
|
| |
|
|
| |
llvm-svn: 174454
|
| |
|
|
| |
llvm-svn: 174453
|
| |
|
|
| |
llvm-svn: 174452
|
| |
|
|
| |
llvm-svn: 174451
|
| |
|
|
| |
llvm-svn: 174450
|
| |
|
|
| |
llvm-svn: 174449
|
| |
|
|
| |
llvm-svn: 174448
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a more natural order of evaluation, and it is very important
for visualization in the static analyzer. Within Xcode, the arrows
will not jump from right to left, which looks very visually jarring.
It also provides a more natural location for dataflow-based diagnostics.
Along the way, we found a case in the analyzer diagnostics where we
needed to indicate that a variable was "captured" by a block.
-fsyntax-only timings on sqlite3.c show no visible performance change,
although this is just one test case.
Fixes <rdar://problem/13016513>
llvm-svn: 174447
|
| |
|
|
|
|
|
| |
pointer in function prologs/epilogs. The opcodes should depend on the
data model (LP64 vs. ILP32) rather than the architecture bit-ness.
llvm-svn: 174446
|
| |
|
|
|
|
|
|
|
| |
We generate one line table for each compilation unit in the object file.
Reviewed by Eric and Kevin.
rdar://problem/13067005
llvm-svn: 174445
|
| |
|
|
| |
llvm-svn: 174444
|
| |
|
|
|
|
|
| |
- This is so that we can easily write XFAIL markers for tests that are known
to fail with versions of libc++ as were shipped with a particular triple.
llvm-svn: 174443
|
| |
|
|
|
|
|
|
|
|
|
| |
is a vararg function.
The original code was examining flag OutputArg::IsFixed to determine whether
CC_MipsN_VarArg or CC_MipsN should be called. This is not correct, since this
flag is often set to false when the function being analyzed is a non-variadic
function.
llvm-svn: 174442
|
| |
|
|
| |
llvm-svn: 174441
|
| |
|
|
|
|
|
|
|
|
| |
- We parse up to the first non-empty non-comment (C++ style) line, otherwise
the format and semantics match what is used for LLVM/Clang tests.
- For now, the only interesting thing to test against is a user supplied
target_triple test parameter.
llvm-svn: 174440
|
| |
|
|
| |
llvm-svn: 174439
|
| |
|
|
| |
llvm-svn: 174438
|
| |
|
|
| |
llvm-svn: 174437
|
| |
|
|
|
|
|
|
| |
(void*)p.
Addresses the false positives similar to the test case.
llvm-svn: 174436
|
| |
|
|
| |
llvm-svn: 174435
|
| |
|
|
| |
llvm-svn: 174434
|
| |
|
|
| |
llvm-svn: 174433
|
| |
|
|
| |
llvm-svn: 174432
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
differentiate between the alignment of the
base point of a load, and the overall alignment of the load. This caused infinite loops in DAG combine with the
original application of this patch.
ORIGINAL COMMIT LOG:
When the target-independent DAGCombiner inferred a higher alignment for a load,
it would replace the load with one with the higher alignment. However, it did
not place the new load in the worklist, which prevented later DAG combines in
the same phase (for example, target-specific combines) from ever seeing it.
This patch corrects that oversight, and updates some tests whose output changed
due to slightly different DAGCombine outputs.
llvm-svn: 174431
|
| |
|
|
|
|
| |
Found by running instcombine on a fabricated test case for the constant folder.
llvm-svn: 174430
|
| |
|
|
|
|
| |
zext( set[ne,eq,gt,ugt] (...) ) type of dag patterns.
llvm-svn: 174429
|
| |
|
|
| |
llvm-svn: 174428
|