- Jun 25, 2009
-
-
Jeffrey Yasskin authored
emitted or the machine code for a function is freed. Chris mentioned that we may also want a notification when a stub is emitted, but that'll be a future change. I intend to use this to tell oprofile where functions are emitted and what lines correspond to what addresses. llvm-svn: 74157
-
Evan Cheng authored
llvm-svn: 74156
-
Chris Lattner authored
llvm-svn: 74155
-
Chris Lattner authored
llvm-svn: 74154
-
Mikhail Glushenkov authored
Factor out common preprocessor-related bits to Makefile.rules. llvm-svn: 74153
-
Evan Cheng authored
llvm-svn: 74152
-
Devang Patel authored
No need to code gen MDNodes llvm-svn: 74150
-
Bill Wendling authored
null. llvm-svn: 74147
-
Dan Gohman authored
llvm-svn: 74146
-
Dan Gohman authored
but for getUniqueExitBlocks. llvm-svn: 74145
-
Owen Anderson authored
llvm-svn: 74143
-
Evan Cheng authored
llvm-svn: 74141
-
Owen Anderson authored
llvm-svn: 74140
-
Daniel Dunbar authored
- Includes some DG tests in test/MC/AsmParser, which are rather primitive since we don't have a -verify mode yet. llvm-svn: 74139
-
Evan Cheng authored
llvm-svn: 74138
-
Owen Anderson authored
llvm-svn: 74137
-
Ted Kremenek authored
llvm-svn: 74136
-
Owen Anderson authored
llvm-svn: 74135
-
Owen Anderson authored
llvm-svn: 74134
-
Devang Patel authored
llvm-svn: 74133
-
Owen Anderson authored
llvm-svn: 74132
-
Ted Kremenek authored
llvm-svn: 74131
-
David Greene authored
Increase limit for OpActions array The OpActions array had a limit of 32 value types, so change it to use MVT::MAX_ALLOWED_VALUETYPE in its declaration and change the accesses to this array to work with a VT.getSimpleVT() that is larger than 32. Also, add a comment to the place where MVT::MAX_ALLOWED_VALUETYPE is defined indicating that it must be a multiple of 32. This is part of the work allow MVT::LAST_VALUETYPE be greater than 32. llvm-svn: 74130
-
Owen Anderson authored
llvm-svn: 74129
-
Ted Kremenek authored
llvm-svn: 74128
-
Anders Carlsson authored
llvm-svn: 74127
-
Fariborz Jahanian authored
look at it later. llvm-svn: 74126
-
Owen Anderson authored
llvm-svn: 74125
-
- Jun 24, 2009
-
-
Evan Cheng authored
llvm-svn: 74121
-
Andreas Bolka authored
llvm-svn: 74120
-
Jeffrey Yasskin authored
llvm-svn: 74119
-
Anders Carlsson authored
llvm-svn: 74118
-
Bob Wilson authored
libraries instead of relinked objects, the interpreter, JIT, and native target libraries were not being linked in to an ocaml program using the ExecutionEngine. llvm-svn: 74117
-
Jeffrey Yasskin authored
llvm-svn: 74116
-
Anders Carlsson authored
llvm-svn: 74115
-
Lang Hames authored
llvm-svn: 74114
-
Owen Anderson authored
llvm-svn: 74113
-
Chris Lattner authored
llvm-svn: 74112
-
Chris Lattner authored
picbase instead of inlining it. llvm-svn: 74111
-
David Greene authored
This increases the maximum for MVT::LAST_VALUETYPE This change doubles the allowable value for MVT::LAST_VALUETYPE. It does this by doing several things. 1. Introduces MVT::MAX_ALLOWED_LAST_VALUETYPE which in this change has a value of 64. This value contains the current maximum for the MVT::LAST_VALUETYPE. 2. Instead of checking "MVT::LAST_VALUETYPE <= 32", all of those uses now become "MVT::LAST_VALUETYPE <= MVT::MAX_ALLOWED_LAST_VALUETYPE" 3. Changes the dimension of the ValueTypeActions from 2 elements to four elements and adds comments ahead of the declaration indicating the it is "(MVT::MAX_ALLOWED_LAST_VALUETYPE/32) * 2". This at least lets us find what is affected if and when MVT::MAX_ALLOWED_LAST_VALUETYPE gets changed. 4. Adds initializers for the new elements of ValueTypeActions. This does NOT add any types in MVT. That would be done separately. This doubles the size of ValueTypeActions from 64 bits to 128 bits and gives us the freedom to add more types for AVX. llvm-svn: 74110
-