- Jul 07, 2011
-
-
Devang Patel authored
llvm-svn: 134643
-
Evan Cheng authored
llvm-svn: 134641
-
Bill Wendling authored
llvm-svn: 134640
-
Akira Hatanaka authored
based on a modifier, split it into two functions. llvm-svn: 134637
-
Akira Hatanaka authored
numbers should be printed instead of symbolic register names in MCAsmStreamer::EmitRegisterName. This is necessary because some versions of GNU assembler won't accept code in which symbolic register names are used in cfi directives. There is no change in behavior unless the flag is explicitly set to true by a backend. llvm-svn: 134635
-
Akira Hatanaka authored
llvm-svn: 134633
-
Akira Hatanaka authored
llvm-svn: 134630
-
Akira Hatanaka authored
llvm-svn: 134629
-
Akira Hatanaka authored
llvm-svn: 134628
-
Evan Cheng authored
llvm-svn: 134627
-
Evan Cheng authored
llvm-svn: 134626
-
Akira Hatanaka authored
before the offset. This change will enable simplification of function MipsRegisterInfo::eliminateFrameIndex. llvm-svn: 134625
-
Akira Hatanaka authored
llvm-svn: 134622
-
Devang Patel authored
If known DebugLocs do not match then two DBG_VALUE machine instructions are not identical. For example, DBG_VALUE 3.310000e+02, 0, !"ds"; dbg:sse.stepfft.c:138:18 @[ sse.stepfft.c:32:10 ] DBG_VALUE 3.310000e+02, 0, !"ds"; dbg:sse.stepfft.c:138:18 @[ sse.stepfft.c:31:10 ] These two MIs represent identical value, 3.31..., for one variable, ds, but they are not identical because the represent two separate instances of inlined variable "ds". llvm-svn: 134620
-
Joerg Sonnenberger authored
llvm-svn: 134617
-
Oscar Fuentes authored
llvm-svn: 134616
-
Douglas Gregor authored
llvm-svn: 134614
-
Cameron Zwarich authored
multiply-accumulate instructions with separate rounding steps. llvm-svn: 134609
-
Evan Cheng authored
llvm-svn: 134608
-
Evan Cheng authored
llvm-svn: 134607
-
Evan Cheng authored
llvm-svn: 134606
-
Chris Lattner authored
llvm-svn: 134601
-
Chris Lattner authored
llvm-svn: 134599
-
Bill Wendling authored
llvm-svn: 134595
-
Lang Hames authored
hasPredecessorHelper function allows predecessors to be cached to speed up repeated invocations. This fixes PR10186. X.isPredecessorOf(Y) now just calls Y.hasPredecessor(X) Y.hasPredecessor(X) calls Y.hasPredecessorHelper(X, Visited, Worklist) with empty Visited and Worklist sets (i.e. no caching over invocations). Y.hasPredecessorHelper(X, Visited, Worklist) caches search state in Visited and Worklist to speed up repeated calls. The Visited set is searched for X before going to the worklist to further search the DAG if necessary. llvm-svn: 134592
-
Evan Cheng authored
Change some ARM subtarget features to be single bit yes/no in order to sink them down to MC layer. Also fix tests. llvm-svn: 134590
-
Bill Wendling authored
llvm-svn: 134577
-
Jim Grosbach authored
So users of a CGI don't have to look up the value directly from the original Record; just like the rest of the convenience values in the class. llvm-svn: 134576
-
Lang Hames authored
llvm-svn: 134573
-
Devang Patel authored
llvm-svn: 134572
-
Evan Cheng authored
Factor ARM triple parsing out of ARMSubtarget. Another step towards making ARM subtarget info available to MC. llvm-svn: 134569
-
Devang Patel authored
llvm-svn: 134568
-
Jakub Staszak authored
llvm-svn: 134566
-
Eli Friedman authored
When tail-merging multiple blocks, make sure to correctly update the live-in list on the merged block to correctly account for the live-outs of all the predecessors. They might not be the same in all cases (the testcase I have involves a PHI node where one of the operands is an IMPLICIT_DEF). Unfortunately, the testcase I have is large and confidential, so I don't have a test to commit at the moment; I'll see if I can come up with something smaller where this issue reproduces. <rdar://problem/9716278> llvm-svn: 134565
-
Jim Grosbach authored
llvm-svn: 134563
-
Devang Patel authored
llvm-svn: 134561
-
Devang Patel authored
llvm-svn: 134559
-
Bill Wendling authored
llvm-svn: 134557
-
Eric Christopher authored
llvm-svn: 134555
-
Owen Anderson authored
vec.insert(vec.begin(), vec[3]); The issue was that vec[3] returns a reference into the vector, which is invalidated when insert() memmove's the elements down to make space. The method needs to specifically detect and handle this case to correctly match std::vector's semantics. Thanks to Howard Hinnant for clarifying the correct behavior, and explaining how std::vector solves this problem. llvm-svn: 134554
-