- May 25, 2010
-
-
Jakob Stoklund Olesen authored
llvm-svn: 104629
-
Jakob Stoklund Olesen authored
llvm-svn: 104628
-
Jakob Stoklund Olesen authored
SubRegIndex instances are now numbered uniquely the same way Register instances are - in lexicographical order by name. llvm-svn: 104627
-
Daniel Dunbar authored
llvm-svn: 104626
-
Dale Johannesen authored
Mon Ping provided; unfortunately bugpoint failed to reduce it, but I think it's important to have a test for this in the suite. 8023512. llvm-svn: 104624
-
Daniel Dunbar authored
.s printer or .o writer. llvm-svn: 104623
-
Daniel Dunbar authored
llvm-svn: 104622
-
Kevin Enderby authored
for the 64-bit version of the Bit Test instruction. llvm-svn: 104621
-
Chris Lattner authored
(DeclStmt 0x3405550 <line:3:4, col:11> 0x34053a0 "int x") instead of: (DeclStmt 0x3405550 <line:3:4, col:11> 0x34053a0 "int x" which has unbalanced parens (PR7228) llvm-svn: 104620
-
Dale Johannesen authored
(oye, a word which should be better known to people writing tree traversals, means grandchild.) llvm-svn: 104619
-
Douglas Gregor authored
llvm-svn: 104618
-
Eric Christopher authored
Fixes rdar://8017638 llvm-svn: 104617
-
Howard Hinnant authored
llvm-svn: 104616
-
Jakob Stoklund Olesen authored
This passes lit tests, but I'll give it a go through the buildbots to smoke out any remaining places that depend on the old SubRegIndex numbering. Then I'll remove NumberHack entirely. llvm-svn: 104615
-
Fariborz Jahanian authored
llvm-svn: 104614
-
Douglas Gregor authored
llvm-svn: 104613
-
Jakob Stoklund Olesen authored
llvm-svn: 104612
-
Jakob Stoklund Olesen authored
The cases in getMatchingSuperRegClass cannot be broken up until the enums have unique values. llvm-svn: 104611
-
Douglas Gregor authored
variables within blocks. We loosely follow GCC's mangling, but since these are always internal symbols the names don't really matter. I intend to revisit block mangling later, because GCC's mangling is rather verbose. <rdar://problem/8015719>. llvm-svn: 104610
-
Fariborz Jahanian authored
methods. (Radar 7987817). llvm-svn: 104608
-
Douglas Gregor authored
derived-to-base conversion on a pointer. Fixes PR7224. llvm-svn: 104607
-
Douglas Gregor authored
llvm-svn: 104606
-
Zonr Chang authored
Add missing implementation to the materialization of VFP misc. instructions (vmrs, vmsr and vmov (immediate)) llvm-svn: 104588
-
Zonr Chang authored
llvm-svn: 104587
-
Douglas Gregor authored
llvm-svn: 104586
-
Douglas Gregor authored
1) Suppress diagnostics as soon as we form the code-completion token, so we don't get any error/warning spew from the early end-of-file. 2) If we consume a code-completion token when we weren't expecting one, go into a code-completion recovery path that produces the best results it can based on the context that the parser is in. llvm-svn: 104585
-
Zhongxing Xu authored
whether the size of the symbolic region is a multiple of the size of T. Fixes PR6123 and PR7217. llvm-svn: 104584
-
Bob Wilson authored
I don't know of any particular reason why that would be important, but neither can I see any reason to disallow it. llvm-svn: 104583
-
Bob Wilson authored
Thumb2 ADD and SUB instructions: allow RSB instructions be changed to set the condition codes, and allow RSBS instructions to be predicated. llvm-svn: 104582
-
John McCall authored
variables should have that linkage. Otherwise, its static local variables should have internal linkage. To avoid computing this excessively, set a function's linkage before we emit code for it. Previously we were assigning weak linkage to the static variables of static inline functions in C++, with predictably terrible results. This fixes that and also gives better linkage than 'weak' when merging is required. llvm-svn: 104581
-
Bob Wilson authored
llvm-svn: 104580
-
Nick Lewycky authored
llvm-svn: 104578
-
Daniel Dunbar authored
IRgen/C++: When mark vtables used, make sure to still append to the VTableUse array if we promote a vtable from being just used to having its definition required. This ensures that we properly inform the consumer about whether the vtable is required or not, previously we could fail to do so when the vtable was in the VTableUses array before the decl which marked it as required. - I think this can be cleaned up, since this means we may notify the consumer about the vtable twice, but I didn't see an easy fix for this without more substantial refactoring. - Doug, please review! llvm-svn: 104577
-
Daniel Dunbar authored
llvm-svn: 104576
-
Howard Hinnant authored
[rand.dist.samp.plinear]. This means we've got a fully tested and functional <random>! 489 tests over 48 sections are passing. :-) The only thing still on my plate in this area is to back-port some of this technology to random_shuffle/shuffle in <algorithm>. That will involve shuffling header bits around (<random> depepends on <algorithm>), but it won't entail that much development (compared to what has been required for <random>). llvm-svn: 104575
-
Jakob Stoklund Olesen authored
llvm-svn: 104574
-
Jakob Stoklund Olesen authored
llvm-svn: 104573
-
Bill Wendling authored
llvm-svn: 104572
-
Jakob Stoklund Olesen authored
llvm-svn: 104571
-
Bob Wilson authored
version of t2MVN already allowed that, but not the register versions. llvm-svn: 104570
-