- Apr 24, 2008
-
-
Dan Gohman authored
llvm-svn: 50196
-
Ted Kremenek authored
llvm-svn: 50195
-
Ted Kremenek authored
When building PathDiagnostics for bug reports, generate a trimmed ExplodedGraph with a single path that BugReport objects can safely walk and introspect. llvm-svn: 50194
-
Anton Korobeynikov authored
llvm-svn: 50193
-
Anton Korobeynikov authored
llvm-svn: 50192
-
Anton Korobeynikov authored
llvm-svn: 50191
-
Anton Korobeynikov authored
llvm-svn: 50190
-
Anton Korobeynikov authored
llvm-svn: 50189
-
- Apr 23, 2008
-
-
Dan Gohman authored
llvm-svn: 50187
-
Chris Lattner authored
return instrs operands didn't match up with function results. llvm-svn: 50182
-
Dan Gohman authored
llvm-svn: 50181
-
Dan Gohman authored
llvm-svn: 50180
-
Devang Patel authored
llvm-svn: 50179
-
rdar://problem/5881148Ted Kremenek authored
Problem: In the recently refactored VisitDeref (which processes dereferences), we were incorrectly skipping the node just generated for the subexpression of the dereference. This was a horrible regression. llvm-svn: 50176
-
Dan Gohman authored
llvm-svn: 50175
-
Dale Johannesen authored
llvm-svn: 50174
-
Anton Korobeynikov authored
llvm-svn: 50173
-
Anton Korobeynikov authored
llvm-svn: 50172
-
Anton Korobeynikov authored
llvm-svn: 50171
-
Anton Korobeynikov authored
llvm-svn: 50170
-
Anton Korobeynikov authored
llvm-svn: 50169
-
Anton Korobeynikov authored
llvm-svn: 50168
-
Anton Korobeynikov authored
Be over-conservative: scan for all used virtual registers and calculate maximal stack alignment in assumption, that there will be spill of vector register. llvm-svn: 50167
-
Anton Korobeynikov authored
llvm-svn: 50166
-
Anton Korobeynikov authored
llvm-svn: 50165
-
Anton Korobeynikov authored
llvm-svn: 50164
-
Anton Korobeynikov authored
llvm-svn: 50163
-
Anton Korobeynikov authored
llvm-svn: 50162
-
Anton Korobeynikov authored
Eastimate required stack alignment early, so we can decide, whether we will need frame pointer or not llvm-svn: 50161
-
Anton Korobeynikov authored
llvm-svn: 50160
-
Anton Korobeynikov authored
llvm-svn: 50159
-
Anton Korobeynikov authored
llvm-svn: 50158
-
Anton Korobeynikov authored
llvm-svn: 50157
-
Anton Korobeynikov authored
llvm-svn: 50156
-
Anton Korobeynikov authored
llvm-svn: 50155
-
Anton Korobeynikov authored
llvm-svn: 50154
-
Anton Korobeynikov authored
llvm-svn: 50153
-
Anton Korobeynikov authored
llvm-svn: 50152
-
Dan Gohman authored
llvm-svn: 50151
-
Ted Kremenek authored
when it is constructed via deserialization. This is done by recording a flag indicating that this is the case, and it deletes these objects by getting the references stored in the ASTContext object. This fixes some memory leaks that occurs when we deserialize translation units from bitcode files. The rationale between having TranslationUnit sometimes own these objects and sometimes not is that a TranslationUnit object can be constructed from state generated by the parser (Preprocessor; semantic analyzer, etc.), and thus in these cases won't own the IdentifierTable or Selectors, etc. During deserialization, there is no Preprocessor, so somebody needs to own these objects in order for them to be properly reclaimed. llvm-svn: 50149
-