- Aug 11, 2010
-
-
Daniel Dunbar authored
MC/ARM: Add basic support for handling predication by parsing it out of the mnemonic into a separate operand form. llvm-svn: 110794
-
Daniel Dunbar authored
llvm-svn: 110793
-
Daniel Dunbar authored
llvm-svn: 110792
-
Daniel Dunbar authored
llvm-mc: Add -show-inst-operands, for dumping the parsed instruction representation before matching. llvm-svn: 110791
-
Daniel Dunbar authored
llvm-svn: 110790
-
Daniel Dunbar authored
llvm-svn: 110789
-
Daniel Dunbar authored
llvm-svn: 110788
-
Evan Cheng authored
llvm-svn: 110787
-
Evan Cheng authored
instructions: dmb, dsb, isb, msr, and mrs. llvm-svn: 110786
-
Evan Cheng authored
memory and synchronization barrier dmb and dsb instructions. - Change instruction names to something more sensible (matching name of actual instructions). - Added tests for memory barrier codegen. llvm-svn: 110785
-
Zhongxing Xu authored
llvm-svn: 110784
-
Daniel Dunbar authored
llvm-svn: 110783
-
Daniel Dunbar authored
llvm-svn: 110782
-
Daniel Dunbar authored
for some reason they have a very odd MCInst form where the operands overlap, but I haven't dug in to find out why yet. llvm-svn: 110781
-
Daniel Dunbar authored
llvm-svn: 110780
-
Daniel Dunbar authored
llvm-svn: 110779
-
Owen Anderson authored
llvm-svn: 110778
-
Sean Callanan authored
expression parser. It is now possible to type: (lldb) expr int $i = 5; $i + 1 (int) 6 (lldb) expr $i + 2 (int) 7 The skeleton for automatic result variables is also implemented. The changes affect: - the process, which now contains a ClangPersistentVariables object that holds persistent variables associated with it - the expression parser, which now uses the persistent variables during variable lookup - TaggedASTType, where I loaded some commonly used tags into a header so that they are interchangeable between different clients of the class llvm-svn: 110777
-
Daniel Dunbar authored
llvm-svn: 110776
-
Daniel Dunbar authored
- We don't recognize double or NEON register names yet -- we don't have the infrastructure to generate the right clobbers for them. llvm-svn: 110775
-
Daniel Dunbar authored
llvm-svn: 110774
-
Douglas Gregor authored
implicit conversion sequences. In particular, model the "standard conversion" from a class to its own type (or a base type) directly as a standard conversion in the normal path *without* trying to determine if there is a valid copy constructor. This appears to match the intent of C++ [over.best.ics]p6 and more closely matches GCC and EDG. As part of this, model non-lvalue reference initialization via user-defined conversion in overloading the same way we handle it in InitializationSequence, separating the "general user-defined conversion" and "conversion to compatible class type" cases. The churn in the overload-call-copycon.cpp test case is because the test case was originally wrong; it assumed that we should do more checking for copy constructors that we actually should, which affected overload resolution. Fixes PR7055. Bootstrapped okay. llvm-svn: 110773
-
Bruno Cardoso Lopes authored
llvm-svn: 110772
-
Bruno Cardoso Lopes authored
Remove 256-bit cast built-ins and make the AVX intrinsic call llvm __builtin_shufflevector with the appropriate arguments llvm-svn: 110771
-
John McCall authored
llvm-svn: 110770
-
Bruno Cardoso Lopes authored
Remove AVX 256-bit unpack and interleave intrinsics now that clang is using __builtin_shufflevector for those llvm-svn: 110769
-
Bruno Cardoso Lopes authored
Remove 256-bit unpack built-ins and make the AVX intrinsic call llvm __builtin_shufflevector with the appropriate arguments llvm-svn: 110768
-
Bruno Cardoso Lopes authored
llvm-svn: 110767
-
Bruno Cardoso Lopes authored
Remove 256-bit shuffle built-ins and make the AVX intrinsic call llvm __builtin_shufflevector with the appropriate arguments llvm-svn: 110766
-
Bill Wendling authored
llvm-svn: 110765
-
John Thompson authored
llvm-svn: 110764
-
Oscar Fuentes authored
llvm-svn: 110763
-
Bill Wendling authored
llvm-svn: 110762
-
Bill Wendling authored
llvm-svn: 110761
-
John McCall authored
where we weren't accounting for the possibility that a @finally block might have internal cleanups and therefore might write to the cleanup destination slot. Fixes <rdar://problem/8293901>. llvm-svn: 110760
-
Rafael Espindola authored
llvm-svn: 110759
-
Dan Gohman authored
make any assumptions about when the two conditions will agree on when to permit the loop to exit. This fixes PR7845. llvm-svn: 110758
-
Daniel Dunbar authored
from inline assembly, except in cases where they had already been seen (in which case they would get added twice). - I can't see how this ever worked... llvm-svn: 110757
-
Daniel Dunbar authored
llvm-svn: 110756
-
Ted Kremenek authored
Have GRCoreEngine record the blocks where analysis was aborted because we visited a block too many times along a given path. This is to support the unreachable code analysis. llvm-svn: 110755
-