- Jul 06, 2015
-
-
Pavel Labath authored
Summary: On windows, global python variables are not automatically passed to child processes. This commit makes sure the default timeout value is available to child processes by passing it directly. I pass the whole dotest_opts value to the children, so we can use the other members as well if we need to do it in the future. Reviewers: amccarth Subscribers: lldb-commits-list Differential Revision: http://reviews.llvm.org/D10895 llvm-svn: 241459
-
Rafael Espindola authored
llvm-svn: 241458
-
Bruce Mitchener authored
Summary: [lldb-mi] Use 'override' on overridden virtual methods. Reviewers: abidh, ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D10959 llvm-svn: 241457
-
Rafael Espindola authored
llvm-svn: 241456
-
Ed Schouten authored
After r241454 landed, libc++'s locale code compiles on CloudABI, with the exception of the following two bits: - CloudABI doesn't have setlocale(), as the C library does not keep track of any global state. The global locale is always set to "C". Disable the call to setlocale() on this system. - Similarly, mbtowc_l() is also not present, as it is also not thread-safe. As CloudABI does not support state-dependent encodings, simply disable that part of the logic. The locale code now compiles out of the box on CloudABI. Differential Revision: http://reviews.llvm.org/D10729 Reviewed by: jroelofs llvm-svn: 241455
-
Ed Schouten authored
The __cloc() function is only present in case the environment does not provide a way to refer to the C locale using a compile-time constant expression. _LIBCPP_GET_C_LOCALE seems to be defined unconditionally. This improves compilation of the locale code on CloudABI. Differential Revision: http://reviews.llvm.org/D10690 Reviewed by: jroelofs llvm-svn: 241454
-
Rafael Espindola authored
llvm-svn: 241453
-
Tobias Grosser authored
This helps us to understand which thread prints which information. llvm-svn: 241452
-
Douglas Katzman authored
llvm-svn: 241451
-
Rafael Espindola authored
Originally added in r139314. Back then it didn't actually get the address, it got whatever value the relocation used: address or offset. The values in different object formats are: * MachO: Always an offset. * COFF: Always an address, but when talking about the virtual address of sections it says: "for simplicity, compilers should set this to zero". * ELF: An offset for .o files and and address for .so files. In the case of the .so, the relocation in not linked to any section (sh_info is 0). We can't really compute an offset. Some API mappings would be: * Use getAddress for everything. It would be quite cumbersome. To compute the address elf has to follow sh_info, which can be corrupted and therefore the method has to return an ErrorOr. The address of the section is also the same for every relocation in a section, so we shouldn't have to check the error and fetch the value for every relocation. * Use a getValue and make it up to the user to know what it is ...
-
Chad Rosier authored
The code in AArch64A57FPLoadBalancing::scavengeRegister() to handle dead defs was not correctly handling aliased registers. E.g. if the dead def was of D2, then S2 was not being marked as unavailable, so it could potentially be used across a live-range in which it would be clobbered. Patch by Geoff Berry <gberry@codeaurora.org>! Phabricator: http://reviews.llvm.org/D10900 llvm-svn: 241449
-
Bruce Mitchener authored
llvm-svn: 241448
-
Rafael Espindola authored
When talking about the virtual address of sections the coff spec says: ... for simplicity, compilers should set this to zero. Otherwise, it is an arbitrary value that is subtracted from offsets during relocation. We don't currently subtract it, so check that it is zero. If some producer does create such files, we can change getRelocationOffset instead. llvm-svn: 241447
-
Daniel Jasper authored
llvm-svn: 241446
-
Simon Pilgrim authored
llvm-svn: 241445
-
Daniel Jasper authored
Before: aaaaaaaaaaaaaaaaaa(aaaaaaaaaaaaaaaa: aaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaa: aaaaaaaaaaaaaaaaaa): aaaaaaaaaaaaaaaaaaaaaa {} After: aaaaaaaaaaaaaaaaaa(aaaaaaaaaaaaaaaa: aaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaa: aaaaaaaaaaaaaaaaaa): aaaaaaaaaaaaaaaaaaaaaa {} llvm-svn: 241444 -
Asaf Badouh authored
pmulhrsw review: http://reviews.llvm.org/D10948 llvm-svn: 241443
-
Petar Jovanovic authored
Add support for resolving MIPS32r6 relocations in MCJIT. Patch by Vladimir Radosavljevic. Differential Revision: http://reviews.llvm.org/D10687 llvm-svn: 241442
-
Abhishek Aggarwal authored
Summary: - In ABIMacOSX_i386.cpp: -- Earlier, only Triple:Arch was used to choose ABI -- Now, Triple:OS is also used along with Triple:Arch - Resolves PR-23718 Change-Id: Id8b1d86dda763241f9e594a1c71252555939af1e Signed-off-by:Abhishek Aggarwal <abhishek.a.aggarwal@intel.com> Reviewers: jasonmolenda, clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D10308 llvm-svn: 241441
-
Rafael Espindola authored
Thanks to Aboud, Amjad for reporting the regression and providing the testcase. llvm-svn: 241440
-
Daniel Jasper authored
__attribute__ was treated as the name of a function definition, with the tokens in parentheses being the parameter list. This formats incorrectly with AlwaysBreakAfterDefinitionReturnType. Fix it by treating __attribute__ like decltype. Patch by Strager Neds, thank you. llvm-svn: 241439
-
Abhishek Aggarwal authored
llvm-svn: 241438
-
Abhishek Aggarwal authored
llvm-svn: 241437
-
Tamas Berghammer authored
llvm-svn: 241436
-
Tamas Berghammer authored
llvm-svn: 241435
-
Tamas Berghammer authored
Previously we accepted a frame as correct result if the PC pointed into an executable section of code. The isse with that approac is that if we calculated PC correctly but messed up the value of CFA then unwinding from the next fram will most likely fail. With this change I modify the logic with keeping the requirement for PC to point to an executable section and also check that we can continue the unwind from the frame we calculated. If continuing from the frame calculated with the primary unwind plan isn't working then fall back to the fallback plan with the hope for a better frame (if the fallback plan won't help then we acceot the frame from the primary plan). Differential revision: http://reviews.llvm.org/D10932 llvm-svn: 241434
-
Yaron Keren authored
and std::move to avoid implicit std::string construction. Patch by Eugene Kosov. llvm-svn: 241433
-
Yaron Keren authored
llvm-svn: 241432
-
Craig Topper authored
[TableGen] Change a couple methods to return an ArrayRef instead of a const std::vector reference. NFC llvm-svn: 241431
-
Craig Topper authored
[TableGen] Change a couple methods to return an ArrayRef instead of a const std::vector reference. NFC llvm-svn: 241430
-
Alexey Bataev authored
Add the next codegen for 'omp cancel' directive: if (__kmpc_cancel()) { __kmpc_cancel_barrier(); <exit construct>; } llvm-svn: 241429 -
Richard Smith authored
an existing using shadow declaration if they define entities of the same kind in different namespaces. We'd previously check this consistently if the using-declaration came after the other declaration, but not if it came before. llvm-svn: 241428
-
Rafael Espindola authored
Before every test was using a section with an address of zero. llvm-svn: 241427
-
Rui Ueyama authored
TLS table header field is supposed to have address and size of TLS table. The linker doesn't have to understand what TLS table is. TLS table's name is always "_tls_used", so if there's that symbol, the linker simply sets that symbol's RVA to the header. The size of the TLS table is always 40 bytes. llvm-svn: 241426
-
Richard Smith authored
llvm-svn: 241425
-
Richard Smith authored
When we see something that looks like a constructor with a return type, only issue one error, not two. llvm-svn: 241424
-
NAKAMURA Takumi authored
llvm-svn: 241423
-
Sanjay Patel authored
llvm-svn: 241422
-
NAKAMURA Takumi authored
llvm-svn: 241421
-
Rui Ueyama authored
This function is called SymbolTable::readObjects, so in order to parallelize that function, we have to make this function thread-safe. llvm-svn: 241420
-