- Feb 25, 2015
-
-
Matthias Braun authored
llvm-svn: 230354
-
Matthias Braun authored
llvm-svn: 230353
-
Tom Stellard authored
We legalize mubuf instructions post-instruction selection, so this code is no longer needed. llvm-svn: 230352
-
Ilia K authored
Add comment in MiSignalTestCase.test_lldbmi_stopped_when_stopatentry_local back and revert expecting string. llvm-svn: 230351
-
Tim Northover authored
The backend should now be able to handle all AAPCS rules based on argument type, which means Clang no longer has to duplicate the register-counting logic and the CodeGen can be significantly simplified. llvm-svn: 230349
-
Tim Northover authored
The logic is almost there already, with our special homogeneous aggregate handling. Tweaking it like this allows front-ends to emit AAPCS compliant code without ever having to count registers or add discarded padding arguments. Only arrays of i32 and i64 are needed to model AAPCS rules, but I decided to apply the logic to all integer arrays for more consistency. llvm-svn: 230348
-
Hafiz Abid Qadeer authored
llvm-svn: 230347
-
Hafiz Abid Qadeer authored
Summary: After recent changes, some code has become redundant. This revision tries to remove the un-used code and tidy up the rest. Following 4 files have been removed. I have updated CMake files and checked that it builds fine on Linux and Windows. Can somebody update the xcode related file accordingly? tools/lldb-mi/MICmnStreamStdinLinux.cpp tools/lldb-mi/MICmnStreamStdinLinux.h tools/lldb-mi/MICmnStreamStdinWindows.cpp tools/lldb-mi/MICmnStreamStdinWindows.h Reviewers: clayborg, ki.stfu Reviewed By: clayborg, ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7834 llvm-svn: 230345
-
Timur Iskhodzhanov authored
llvm-svn: 230344
-
Tobias Grosser authored
This reverts commit r230062. Debian stable (wheezy) ships still with cmake 2.8.9. The commit broke my LLVM/Polly buildbot, to my knowledge our only Linux+cmake buildbot. llvm-svn: 230343
-
Sanjay Patel authored
llvm-svn: 230342
-
Hans Wennborg authored
This caused PR22674, failing this assert: Instructions.h:2281: llvm::Value* llvm::PHINode::getOperand(unsigned int) const: Assertion `i_nocapture < OperandTraits<PHINode>::operands(this) && "getOperand() out of range!"' failed. llvm-svn: 230341
-
Johannes Doerfert authored
This is the code generation for region statements that are created when non-affine control flow was present in the input. A new generator, similar to the block or vector generator, for regions is used to traverse and copy the region statement and to adjust the control flow inside the new region in the end. llvm-svn: 230340
-
Michael Kuperstein authored
This should have gone into r230334. llvm-svn: 230339
-
Sanjay Patel authored
llvm-svn: 230338
-
Johannes Doerfert authored
llvm-svn: 230337
-
Johannes Doerfert authored
llvm-svn: 230336
-
Johannes Doerfert authored
llvm-svn: 230335
-
- Feb 24, 2015
-
-
Michael Kuperstein authored
This fixes the original issue in PR22655, but not the secondary one. llvm-svn: 230334
-
Michael Wong authored
Commit patch for PR19649. Set the correct sign of wide character for literals based on underlying type of wchar_t. Reviewed: http://reviews.llvm.org/D7559 Patch by Rachel Craig; Test cases by Hubert Tong. llvm-svn: 230333
-
Hal Finkel authored
For almost all node types, if the target requested custom lowering, and LowerOperation returned its input, we'd treat the original node as legal. This did not work, however, for many loads and stores, because they follow slightly different code paths, and we did not account for the possibility of LowerOperation returning its input at those call sites. I think that we now handle this consistently everywhere. At the call sites in LegalizeDAG, we used to assert in this case, so there's no functional change for any existing code there. For the call sites in LegalizeVectorOps, this really only affects whether or not we set Changed = true, but I think makes the semantics clearer. No test case here, but it will be covered by an upcoming PowerPC commit adding QPX support. llvm-svn: 230332
-
Alexey Bataev authored
__kmpc_omp_flush() runtime library now has only one argument and is not a vararg anymore. This update makes the codegen compatible with these changes. llvm-svn: 230331
-
Marshall Clow authored
Make the forward declaration for array swap have the same inline/visibility attributes as the definition. Thanks to Steven Wu for the catch. llvm-svn: 230330
-
Johannes Doerfert authored
This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
-
Johannes Doerfert authored
llvm-svn: 230328
-
Toma Tabacu authored
Summary: Separated some instruction and pseudo-instruction definitions from InstAlias definitions, added banner for pseudo-instructions and removed a redundant whitespace from a pseudo-instruction definition. No functional change. Reviewers: dsanders Reviewed By: dsanders Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D7552 llvm-svn: 230327
-
Johannes Doerfert authored
llvm-svn: 230326
-
Johannes Doerfert authored
With this patch we allow the SCoP detection to detect regions as SCoPs which have non-affine control flow inside. All non-affine regions are tracked and later accessible to the ScopInfo. As there is no real difference, non-affine branches as well as floating point branches are covered (and both called non-affine control flow). However, the detection is restricted to overapproximate only loop free regions. llvm-svn: 230325
-
Renato Golin authored
Sanitizers work on ancient kernels and were depending on types existing. When those types were removed, the sanitizer build broke. See bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59009 for more information. This patch fixes it by isolating the need for those types only when the feature is actually needed, thus allowing one to compile the kernel with or without that change, irrespective of its version. Patch by Christophe Lyon. llvm-svn: 230324
-
Kuba Brecka authored
The buildbot failed to build with error: variable ‘enable_fp’ set but not used [-Werror=unused-but-set-variable] let's add a `(void)enable_fp;`. llvm-svn: 230323 -
Eric Fiselier authored
llvm-svn: 230322
-
Ilia K authored
Summary: Add -exec-abort command + test. Also, I had fixed an error, when lldb-mi exits on eStateExited. With current patch we can re-run target: ``` -file-exec-and-symbols hello ^done -exec-run ^running *stopped,reason="breakpoint-hit"... -exec-abort ^done *stopped,reason="exited-normally"... <- program exits -exec-run <- run again ^running *stopped,reason="breakpoint-hit"... ``` All tests pass on OS X. Reviewers: zturner, emaste, abidh, clayborg Reviewed By: abidh, clayborg Subscribers: lldb-commits, emaste, zturner, clayborg, abidh Differential Revision: http://reviews.llvm.org/D7794 llvm-svn: 230321
-
Ilia K authored
llvm-svn: 230320
-
Tamas Berghammer authored
This new class makes it easier to change the timeout of a GDBRemoteCommunication instance for a short time and then restore it to its original value. Differential revision: http://reviews.llvm.org/D7826 llvm-svn: 230319
-
Kuba Brecka authored
In debug mode (COMPILER_RT_DEBUG=On), we still build with -fomit-frame-pointer and wrap_ioctl doesn't set up a proper stack frame. In release mode it does, because ioctl_common_pre gets inlined into wrap_ioctl and it uses the COMMON_INTERCEPTOR_READ_RANGE macro which in the end calls GET_CURRENT_FRAME and that forces the compiler to generate a stack frame for the function. Not having a proper stack frame breaks the unwinder. This patch forces to generate a frame pointer (via ENABLE_FRAME_POINTER macro). Reviewed at http://reviews.llvm.org/D7815 llvm-svn: 230318
-
Kuba Brecka authored
When AddressSanitizer only a single dynamic alloca and no static allocas, due to an early exit from FunctionStackPoisoner::poisonStack we forget to unpoison the dynamic alloca. This patch fixes that. Reviewed at http://reviews.llvm.org/D7810 llvm-svn: 230317
-
Kuba Brecka authored
When AddressSanitizer only a single dynamic alloca and no static allocas, due to an early exit from FunctionStackPoisoner::poisonStack we forget to unpoison the dynamic alloca. This patch fixes that. Reviewed at http://reviews.llvm.org/D7810 llvm-svn: 230316
-
Michael Kuperstein authored
MSVC does not support C99 _Complex. ICC, however, does support it on windows x86_64, and treats it, for purposes of parameter passing, as equivalent to a struct containing two fields (for the real and imaginary part). Differential Revision: http://reviews.llvm.org/D7825 llvm-svn: 230315
-
Manuel Klimek authored
Fixes multiple crashes where a non-canonical decl would be used as key in a lookup. llvm-svn: 230314
-
Craig Topper authored
[X86] Remove the AbsMem32 type from the assembly parser. Only really need the 16-bit version which will automatically get prioritized over AbsMem. llvm-svn: 230313
-