- Jun 28, 2012
-
-
Jack Carter authored
It takes advantage of r159299 which introduces relocation support for N64. elf-dump needed to be upgraded to support N64 relocations as well. This passes make check. Jack llvm-svn: 159301
-
Chad Rosier authored
llvm-svn: 159300
-
Jack Carter authored
which many Mips 64 ABIs use than for O64 which many if not all other target ABIs use. Most architectures have the following 64 bit relocation record format: typedef struct { Elf64_Addr r_offset; /* Address of reference */ Elf64_Xword r_info; /* Symbol index and type of relocation */ } Elf64_Rel; typedef struct { Elf64_Addr r_offset; Elf64_Xword r_info; Elf64_Sxword r_addend; } Elf64_Rela; Whereas N64 has the following format: typedef struct { Elf64_Addr r_offset;/* Address of reference */ Elf64_Word r_sym; /* Symbol index */ Elf64_Byte r_ssym; /* Special symbol */ Elf64_Byte r_type3; /* Relocation type */ Elf64_Byte r_type2; /* Relocation type */ Elf64_Byte r_type; /* Relocation type */ } Elf64_Rel; typedef struct { Elf64_Addr r_offset;/* Address of reference */ Elf64_Word r_sym; /* Symbol index */ Elf64_Byte r_ssym; /* Special symbol */ Elf64_Byte r_type3; /* Relocation type */ Elf64_Byte r_type2; /* Relocation type */ Elf64_Byte r_type; /* Relocation type */ Elf64_Sxword r_addend; } Elf64_Rela; The structure is the same size, but the r_info data element is now 5 separate elements. Besides the content aspects, endian byte reordering will be different for the area with each element being endianized separately. I treat this as generic and continue to pass r_type as an integer masking and unmasking the byte sized N64 values for N64 mode. I've implemented this and it causes no affect on other current targets. This passes make check. Jack llvm-svn: 159299
-
Greg Clayton authored
Added the ability to read the dSYM plist file with source remappings even when DebugSymbols isn't used to find the dSYM. We now parse the plist as XML in the MacOSX symbol vendor. Added the ability to get a section load address given a target which is needed for a previous checking which saves crashlogs. llvm-svn: 159298
-
- Jun 27, 2012
-
-
Timur Iskhodzhanov authored
llvm-svn: 159296
-
Eli Friedman authored
llvm-svn: 159295
-
Dmitry Vyukov authored
llvm-svn: 159294
-
Fariborz Jahanian authored
property retains a block object as it could be on the stack. // rdar://11761511 llvm-svn: 159293
-
Richard Smith authored
llvm-svn: 159292
-
Greg Clayton authored
Fixed the "target modules list" to not crash in Debug builds due to an assertion where the mutex in the "module_list" local variable would assert when the lldb_private::Mutex would destruct. What was happening was the mutex in the module list was being locked by a local locker object and then "module_list" would get destroyed before the locker and the locker still had the mutex locked which would cause the pthread call to destroy the mutex to fail with "Resource busy" and it would cause a mutex leak. llvm-svn: 159291
-
Richard Smith authored
before, so we don't incorrectly think arguments of function type are non-POD. llvm-svn: 159290
-
Greg Clayton authored
Modify the ranges_access() helper function to be able to lookup the address range in a block given an address. Since blocks can have multiple discontiguous ranges, it helps to be able to get the current address range for the current block in a frame. This can be used in code like: curr_block_range = lldb.frame.block.range[lldb.frame.addr] llvm-svn: 159289
-
Greg Clayton authored
llvm-svn: 159288
-
Greg Clayton authored
Make the IsValid() operator for SBLineEntry "do the right thing" by returning true if the line entry is valid, not just if the opaque pointer to lldb_private::LineEntry is non NULL. llvm-svn: 159287
-
Greg Clayton authored
Added a "save_crashlog" command to the lldb.macosx.crashlog package that allow you to dump your current process state out to a crash log file. This will dump all of the target module information with all load addresses, UUID values, and shared library paths, as well as all thread stacks and the crash log header. This will make it easy for us to save the current state of a process and then reload it later into LLDB. llvm-svn: 159286
-
Greg Clayton authored
llvm-svn: 159285
-
Greg Clayton authored
llvm-svn: 159284
-
Greg Clayton authored
llvm-svn: 159283
-
Fariborz Jahanian authored
when it appears to be unused and occurs in a header. // rdar://11202617 llvm-svn: 159282
-
Anshuman Dasgupta authored
Patch by Ivan Llopard! llvm-svn: 159281
-
Rafael Espindola authored
being updated. Will fix that in a second. llvm-svn: 159280
-
Rafael Espindola authored
llvm-svn: 159279
-
Dmitry Vyukov authored
llvm-svn: 159278
-
Jim Ingham authored
Make a way to set the result status for Python defined commands, and don't overwrite the status of the result if the python command has set it. llvm-svn: 159273
-
Matt Beaumont-Gay authored
Original commit message: If a constant or a function has linkonce_odr linkage and unnamed_addr, mark it hidden. Being linkonce_odr guarantees that it is available in every dso that needs it. Being a constant/function with unnamed_addr guarantees that the copies don't have to be merged. llvm-svn: 159272
-
Dmitri Gribenko authored
Remove unsigned and a pointer from a comment token (so that each token can have only one semantic string value attached to it), at a cost of adding an additional token. llvm-svn: 159270
-
Dmitri Gribenko authored
Comment lexer: counting backwards from token end is thought to be confusing. We already have a pointer to the beginning of the token, so use it to extract the text instead. llvm-svn: 159269
-
Duncan Sands authored
requiring a module. Original patch by Sunay Ismail, simplified by Arnaud de Grandmaison, then complicated by me (if a triple was specified on the command line, output help for that triple, not for the default). llvm-svn: 159268
-
Dmitri Gribenko authored
llvm-svn: 159267
-
Dmitry Vyukov authored
llvm-svn: 159266
-
Duncan Sands authored
before the expression root. Any existing operators that are changed to use one of them needs to be moved between it and the expression root, and recursively for the operators using that one. When I rewrote RewriteExprTree I accidentally inverted the logic, resulting in the compacting going down from operators to operands rather than up from operands to the operators using them, oops. Fix this, resolving PR12963. llvm-svn: 159265
-
Dmitry Vyukov authored
llvm-svn: 159264
-
Dmitry Vyukov authored
llvm-svn: 159263
-
Axel Naumann authored
llvm-svn: 159262
-
Chandler Carruth authored
directories from the cmake file. Dunno what the history is here, but we're not using it. More refactorings to come here. llvm-svn: 159261
-
Chandler Carruth authored
llvm-svn: 159260
-
Richard Barton authored
llvm-svn: 159259
-
Chandler Carruth authored
'check-llvm'. Don't worry! 'check' still works! =] To rationalize the names of targets used to run tests, the vague plan is the following: make check-llvm # run LLVM reg/unit tests (currently 'check') make check-clang # run Clang reg/unit tests (currently 'clang-test') make check-rt # run CompilerRT reg/unit tests make check-asan # run ASan reg/unit tests (subset of -rt) make check-tsan # run TSan reg/unit tests (subset of -rt) make check-all # run as much of the above as is available The last one respects what projects are checked out and built for a given tree. Personally, I would like to eventually make 'check' be an alias for 'check-all'. For now however, it is an alias for 'check-llvm', and thus no behavior has changed. While this patch and my plan only really apply to CMake, I think it might be good to similarly rationalize the naming scheme for the Make builds. llvm-svn: 159258
-
Richard Barton authored
llvm-svn: 159257
-
Axel Naumann authored
add interface for removing a FileEntry from the cache. Forces a re-read the contents from disk, e.g. because a tool (like cling) wants to pick up a modified file. llvm-svn: 159256
-