- Jun 05, 2014
-
-
Richard Smith authored
llvm-svn: 210219
-
Nick Lewycky authored
llvm-svn: 210218
-
Hans Wennborg authored
They should be initialized when they're exported. Differential Revision: http://reviews.llvm.org/D4020 llvm-svn: 210217
-
Greg Fitzgerald authored
llvm-svn: 210216
-
Hans Wennborg authored
We would previously assert here when trying to figure out the section for the global. This makes us handle the situation more gracefully since the IR isn't malformed. Differential Revision: http://reviews.llvm.org/D4022 llvm-svn: 210215
-
Alexey Samsonov authored
llvm-svn: 210214
-
Todd Fiala authored
lldb-gdbserver and NativeProcessProtocol will use MemoryRegionInfo but don't want to pull in Process.h. Pull this declaration and definition out into its own header. llvm-svn: 210213
-
Alexey Samsonov authored
Share mode code between these functions and re-structure them in a way which shows how similar they actually are. The latter function works well with literals of multi-byte chars and does a GlobalVariable name mangling (if global strings are non-writable). No functionality change. llvm-svn: 210212
-
Richard Smith authored
allows allocations and deallocations to be optimized out. llvm-svn: 210211
-
David Majnemer authored
Signals may result in nanosleep returning with only some of the requested sleeping performed. Utilize nanosleep's "time-remaining" out parameter to continue sleeping when this occurs. llvm-svn: 210210
-
Tobias Grosser authored
llvm-svn: 210208
-
Rafael Espindola authored
llvm-svn: 210206
-
Rafael Espindola authored
Thanks to rnk for the suggestion. llvm-svn: 210205
-
Rafael Espindola authored
llvm-svn: 210204
-
Rafael Espindola authored
llvm-svn: 210203
-
Peter Collingbourne authored
llvm-svn: 210202
-
Yaron Keren authored
When JITting a large project such as Boost it's quite hard to figure out the problematic inline asm without debug location. This patch provides debug location printout before the JIT aborts due to inline asm. printDebugLoc() was exposed from MachineInstr.cpp and reused here. If the JIT run with debug info, don't bomb on DBG_VALUE but ignore them. http://reviews.llvm.org/D3416 llvm-svn: 210201
-
David Blaikie authored
XFAIL: test/DebugInfo/missing-abstract-variable.ll on mips and ppc64 due to an inlined parameter that goes missing. llvm-svn: 210200
-
Sergey Matveev authored
Based on a patch by Stephan Bergmann. llvm-svn: 210199
-
David Majnemer authored
Tested for compatibility with VS2013. llvm-svn: 210198
-
David Majnemer authored
Straightforward implementation of UDLs, it's compatible with VS "14". This nearly completes our implementation of C++ name mangling for the MS-ABI. llvm-svn: 210197
-
Todd Fiala authored
Added two new tests: one to verify that a test exe heap address returned is readable and writeable, and a similar one to verify a test exe stack address is readable and writeable. Ran the main.cpp test exe code through the Xcode re-indenter. I was using TextMate to edit the test's C++ code alongside the Python code but last check-in found that it was not handling tabs/indentation the way I am intending it. Modified test exe to require C++11. Refactored gdb remote python code's handling of memory region info into more re-usable methods. llvm-svn: 210196
-
Nico Weber authored
The maximum alignment on arm is 8, not 16 like on x86. Use alignof(max_align_t) to make the test work in both cases. llvm-svn: 210195
-
Saleem Abdulrasool authored
Add parenthesis as suggested by GCC. llvm-svn: 210194
-
Saleem Abdulrasool authored
Case insensitive case preserving file systems are not a good choice for development. llvm-svn: 210193
-
- Jun 04, 2014
-
-
Saleem Abdulrasool authored
Add support to llvm-readobj to decode Windows ARM Exception Handling data. This uses the previously added datastructures to decode the information into a format that can be used by tests. This is a necessary step to add support for emitting Windows on ARM exception handling information. A fair amount of formatting inspiration is drawn from the Win64 EH printer as well as the ARM EHABI printer. This allows for a reasonably thorough look into the encoded data. llvm-svn: 210192
-
Saleem Abdulrasool authored
Add a helper print method to print a boolean value as "Yes" or "No". This is intended to be used by the Windows ARM EH printer. llvm-svn: 210191
-
Saleem Abdulrasool authored
This is purely a documentation/whitespace cleanup for the format support functions. The current style does not duplicate the function/class names in the documentation; conform to this style. Additionally, there was a large amount of duplication of comments that added no real value. Use block comments for the related sets of functions which are used for type deduction and parameter container classes. No functional change. llvm-svn: 210190
-
Saleem Abdulrasool authored
Replicate the fact that ARM::WinEH::RuntimeFunction purposefully does not merge functions to accommodate raw data access use cases in tools such as readobj. Pointed out by Renato during post-commit review. No functional change. llvm-svn: 210189
-
Nico Weber authored
libc++ currently relies on undefined initialization order of global initializers when using gcc: 1. __start_std_streams in iostream.cpp calls locale::id::_init, which assigns an id to each locale::facet in an initializer 2. Every facet has a static locale::id id, whose constructor sets the facet's id to 0 If 2 runs after 1, it clobbers the facet's assigned consecutive id, causing exceptions to be thrown when e.g. running code like "cout << endl". To fix this, let _LIBCPP_CONSTEXPR evaluate to "constexpr" instead of nothing with gcc. locale::id's constructor is marked _LIBCPP_CONSTEXPR, which ensures that it won't get an initializer that could potentially run after the iostream.cpp initializer. (This remains broken when building with msvc.) Also switch constexpr-specific code in bitset to use __SIZEOF_SIZE_T__ instead of __SIZE_WIDTH__, because gcc doesn't define the latter. Pair-programmed/debugged with Dana Jansens. llvm-svn: 210188
-
Todd Fiala authored
Added test stub for collecting a code, heap and stack address. Added test to verify that the code address returns a readable, executable memory region and that the memory region range was indeed the one that the code belonged to. llvm-svn: 210187
-
Rafael Espindola authored
This patch implements two things: 1. If we know one number is positive and another is negative, we return true as signed addition of two opposite signed numbers will never overflow. 2. Implemented TODO : If one of the operands only has one non-zero bit, and if the other operand has a known-zero bit in a more significant place than it (not including the sign bit) the ripple may go up to and fill the zero, but won't change the sign. e.x - (x & ~4) + 1 We make sure that we are ignoring 0 at MSB. Patch by Suyog Sarda. llvm-svn: 210186 -
Todd Fiala authored
llvm-svn: 210185
-
Alexander Musman authored
Parsing this clause, allowing it on directive ‘omp simd’ and semantic checks. llvm-svn: 210184
-
Daniel Jasper authored
These are commonly used to structure things like enums or long braced lists. There doesn't seem to be a good reason to have the behavior in such structures be different from the behavior between statements. llvm-svn: 210183
-
Tilmann Scheller authored
No change in functionality. llvm-svn: 210182
-
Tilmann Scheller authored
Variable names should start with an upper case letter. No change in functionality. llvm-svn: 210181
-
Evgeniy Stepanov authored
Reset coverage data on fork(). For memory-mapped mode (coverage_direct=1) this helps avoid loss of data (before this change two processes would write to the same file simultaneously). For normal mode, this reduces coverage dump size, because PCs from the parent process are no longer inherited by the child. llvm-svn: 210180
-
Tobias Grosser authored
We do this currently only for test cases where we have integer offsets that clearly access array dimensions out-of-bound. -; for (long i = 0; i < n; i++) -; for (long j = 0; j < m; j++) -; for (long k = 0; k < o; k++) +; for (long i = 0; i < n - 3; i++) +; for (long j = 4; j < m; j++) +; for (long k = 0; k < o - 7; k++) ; A[i+3][j-4][k+7] = 1.0; This will be helpful if we later want to simplify the access functions under the assumption that they do not access memory out of bounds. llvm-svn: 210179
-
Patrik Hagglund authored
llvm-svn: 210178
-