- Feb 06, 2013
-
-
Evan Cheng authored
llvm-svn: 174482
-
Bill Wendling authored
Fix the 'operator==' and 'hasAttributes' queries to take into account target-dependent attributes. llvm-svn: 174481
-
Bill Wendling authored
This is useful when parsing an object that references multiple attribute groups. N.B. If both builders have alignments specified, then they should match! llvm-svn: 174480
-
Manman Ren authored
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
-
Daniel Dunbar authored
- 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
-
Chad Rosier authored
rdar://13153516 llvm-svn: 174477
-
rdar://problem/11109570Greg Clayton authored
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
-
Daniel Dunbar authored
- The trickery can confuse more basic source processors, in particular the Unix conformance tool that wants to scan headers. llvm-svn: 174475
-
Greg Clayton authored
Fixed the TestSourceManager.py test case to not fail. It was using the "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
-
Eli Bendersky authored
llvm-svn: 174473
-
Michael Gottesman authored
\end paranoia. llvm-svn: 174471
-
Daniel Dunbar authored
- Otherwise, we never were actually linking against the right library when building the test applications. llvm-svn: 174470
-
Daniel Dunbar authored
llvm-svn: 174469
-
Anna Zaks authored
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
-
Bill Wendling authored
llvm-svn: 174467
-
Renato Golin authored
llvm-svn: 174466
-
Eli Bendersky authored
llvm-svn: 174465
-
Eli Bendersky authored
llvm-svn: 174464
-
Eli Bendersky authored
llvm-svn: 174463
-
Eli Bendersky authored
a setter and fix some comments. llvm-svn: 174462
-
Michael Gottesman authored
Changed CGObjCMac.cpp to add the marker externally_initialized to 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
-
- Feb 05, 2013
-
-
rdar://12568983Bob Wilson authored
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
-
Daniel Dunbar authored
llvm-svn: 174459
-
Andrew Trick authored
This reverts commit a33e1fafac7fedb1b080ef07ddf9ad6ddff3a830. This unit test crashes on Darwon. It needs to be temporarily reverted to unblock the test infrastructure. llvm-svn: 174458
-
Bill Wendling authored
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
-
Jason Molenda authored
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
-
Daniel Dunbar authored
llvm-svn: 174454
-
Daniel Dunbar authored
llvm-svn: 174453
-
Daniel Dunbar authored
llvm-svn: 174452
-
Daniel Dunbar authored
llvm-svn: 174451
-
Daniel Dunbar authored
llvm-svn: 174450
-
Ted Kremenek authored
llvm-svn: 174449
-
Douglas Gregor authored
llvm-svn: 174448
-
Ted Kremenek authored
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
-
Eli Bendersky authored
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
-
Manman Ren authored
We generate one line table for each compilation unit in the object file. Reviewed by Eric and Kevin. rdar://problem/13067005 llvm-svn: 174445
-
Daniel Dunbar authored
llvm-svn: 174444
-
Daniel Dunbar authored
- 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
-
Akira Hatanaka authored
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
-
Douglas Gregor authored
llvm-svn: 174441
-