- Jan 23, 2013
-
-
NAKAMURA Takumi authored
llvm-svn: 173240
-
NAKAMURA Takumi authored
llvm-svn: 173239
-
NAKAMURA Takumi authored
llvm-svn: 173238
-
NAKAMURA Takumi authored
It fixes --vg-leak. llvm-svn: 173237
-
NAKAMURA Takumi authored
IRTests/ConstantsTest.cpp: AsInstructionsTest: Delete each instruction immediately if it is not linked. llvm-svn: 173236
-
NAKAMURA Takumi authored
llvm-svn: 173235
-
NAKAMURA Takumi authored
llvm-svn: 173234
-
NAKAMURA Takumi authored
llvm-svn: 173233
-
Michael J. Spencer authored
ErrorOr<void> represents an operation that returns nothing, but can still fail. It should be used in cases where you need the aditional user data that ErrorOr provides over error_code. llvm-svn: 173209
-
- Jan 22, 2013
-
-
NAKAMURA Takumi authored
llvm-svn: 173144
-
NAKAMURA Takumi authored
llvm-svn: 173127
-
NAKAMURA Takumi authored
llvm-svn: 173123
-
- Jan 21, 2013
-
-
Michael Ilseman authored
A SparseMultiSet adds multiset behavior to SparseSet, while retaining SparseSet's desirable properties. Essentially, SparseMultiSet provides multiset behavior by storing its dense data in doubly linked lists that are inlined into the dense vector. This allows it to provide good data locality as well as vector-like constant-time clear() and fast constant time find(), insert(), and erase(). It also allows SparseMultiSet to have a builtin recycler rather than keeping SparseSet's behavior of always swapping upon removal, which allows it to preserve more iterators. It's often a better alternative to a SparseSet of a growable container or vector-of-vector. llvm-svn: 173064
-
Michael J. Spencer authored
llvm-svn: 173004
-
- Jan 20, 2013
-
-
Benjamin Kramer authored
Michael, can this test be ported to C++03? llvm-svn: 172996
-
Michael J. Spencer authored
llvm-svn: 172991
-
- Jan 16, 2013
-
-
Peter Collingbourne authored
In r143502, we renamed getHostTriple() to getDefaultTargetTriple() as part of work to allow the user to supply a different default target triple at configure time. This change also affected the JIT. However, it is inappropriate to use the default target triple in the JIT in most circumstances because this will not necessarily match the current architecture used by the process, leading to illegal instruction and other such errors at run time. Introduce the getProcessTriple() function for use in the JIT and its clients, and cause the JIT to use it. On architectures with a single bitness, the host and process triples are identical. On other architectures, the host triple represents the architecture of the host CPU, while the process triple represents the architecture used by the host CPU to interpret machine code within the current process. For example, when executing 32-bit code on a 64-bit Linux machine, the host triple may be 'x86_64-unknown-linux-gnu', while the process triple may be 'i386-unknown-linux-gnu'. This fixes JIT for the 32-on-64-bit (and vice versa) build on non-Apple platforms. Differential Revision: http://llvm-reviews.chandlerc.com/D254 llvm-svn: 172627
-
Evgeniy Stepanov authored
llvm-svn: 172615
-
Evgeniy Stepanov authored
llvm-svn: 172614
-
- Jan 14, 2013
-
-
Dmitri Gribenko authored
llvm-svn: 172474
-
David Greene authored
Use const_cast<> to avoid cast-away-const errors. llvm-svn: 172464
-
- Jan 12, 2013
-
-
Benjamin Kramer authored
The folding set details can be subtle and broke twice in the last couple of weeks. llvm-svn: 172313
-
- Jan 11, 2013
-
-
Eli Bendersky authored
Patch by Michael Muller. llvm-svn: 172214
-
- Jan 10, 2013
-
-
Dmitri Gribenko authored
llvm-svn: 172108
-
Dmitri Gribenko authored
llvm-svn: 172107
-
Jakub Staszak authored
llvm-svn: 172105
-
David Greene authored
Use memcpy to do type punning instead of a cast. A cast or similar operation through a union breaks strict aliasing rules. llvm-svn: 172081
-
- Jan 07, 2013
-
-
Shuxin Yang authored
llvm-svn: 171764
-
Chandler Carruth authored
library rename. llvm-svn: 171747
-
Chandler Carruth authored
implementation lives already. llvm-svn: 171746
-
- Jan 05, 2013
-
-
Chandler Carruth authored
Fixes the CMake build. It took me cutting and pasting this before I managed to see the missing character. =] llvm-svn: 171589
-
Jakob Stoklund Olesen authored
This is similar to the existing Recycler allocator, but instead of recycling individual objects from a BumpPtrAllocator, arrays of different sizes can be allocated. llvm-svn: 171581
-
Chandler Carruth authored
wall time, user time, and system time since a process started. For walltime, we currently use TimeValue's interface and a global initializer to compute a close approximation of total process runtime. For user time, this adds support for an somewhat more precise timing mechanism -- clock_gettime with the CLOCK_PROCESS_CPUTIME_ID clock selected. For system time, we have to do a full getrusage call to extract the system time from the OS. This is expensive but unavoidable. In passing, clean up the implementation of the old APIs and fix some latent bugs in the Windows code. This might have manifested on Windows ARM systems or other systems with strange 64-bit integer behavior. The old API for this both user time and system time simultaneously from a single getrusage call. While this results in fewer system calls, it also results in a lower precision user time and if only user time is desired, it introduces a higher overhead. It may be worthwhile to switch some of the pass timers to not track system time and directly track user and wall time. The old API also tracked walltime in a confusing way -- it just set it to the current walltime rather than providing any measure of wall time since the process started the way buth user and system time are tracked. The new API is more consistent here. The plan is to eventually implement these methods for a *child* process by using the wait3(2) system call to populate an rusage struct representing the whole subprocess execution. That way, after waiting on a child process its stats will become accurate and cheap to query. llvm-svn: 171551
-
- Jan 04, 2013
-
-
Jakob Stoklund Olesen authored
The iplist::clear() function can be quite expensive because it traverses the entire list, calling deleteNode() and removeNodeFromList() on each element. If node destruction and deallocation can be handled some other way, clearAndLeakNodesUnsafely() can be used to jettison all nodes without bringing them into cache. The function name is meant to be ominous. llvm-svn: 171540
-
Nick Kledzik authored
Update test case to verify flow sequence is written as a flow sequence. llvm-svn: 171514
-
- Jan 02, 2013
-
-
Michael J. Spencer authored
* Add support for specifying the alignment to use. * Add the concept of native endianness. Used for unaligned native types. The native alignment and read/write simplification is based on a patch by Richard Smith. llvm-svn: 171406
-
Chandler Carruth authored
into their new header subdirectory: include/llvm/IR. This matches the directory structure of lib, and begins to correct a long standing point of file layout clutter in LLVM. There are still more header files to move here, but I wanted to handle them in separate commits to make tracking what files make sense at each layer easier. The only really questionable files here are the target intrinsic tablegen files. But that's a battle I'd rather not fight today. I've updated both CMake and Makefile build systems (I think, and my tests think, but I may have missed something). I've also re-sorted the includes throughout the project. I'll be committing updates to Clang, DragonEgg, and Polly momentarily. llvm-svn: 171366
-
Chandler Carruth authored
llvm-svn: 171363
-
- Jan 01, 2013
-
-
Chandler Carruth authored
users over to the new one. No sense maintaining this "compatibility" layer it seems. llvm-svn: 171331
-
Chandler Carruth authored
Implement the old API in terms of the new one. This simplifies the implementation on Windows which can now re-use the self_process's once initialization. llvm-svn: 171330
-