- Jan 10, 2010
-
-
Chris Lattner authored
nicer than passing around two const char*'s. llvm-svn: 93094
-
Julien Lerouge authored
llvm-svn: 93093
-
Chris Lattner authored
llvm-svn: 93092
-
Chris Lattner authored
llvm-svn: 93091
-
Chris Lattner authored
llvm-svn: 93090
-
Chris Lattner authored
commonIntCastTransforms into the callers, eliminating a switch, and allowing the static predicate methods to be moved down to live next to the corresponding function. No functionality change. llvm-svn: 93089
-
Daniel Dunbar authored
llvm-svn: 93088
-
Daniel Dunbar authored
llvm-svn: 93087
-
Daniel Dunbar authored
-weak_reference_mismatches is not present, it is the default. llvm-svn: 93086
-
Chris Lattner authored
llvm-svn: 93085
-
Chris Lattner authored
llvm-svn: 93084
-
rdar://7520940Chris Lattner authored
import other headers within the same framework with the full framework path, not with a relative include. llvm-svn: 93083
-
Chris Lattner authored
llvm-svn: 93082
-
- Jan 09, 2010
-
-
Ted Kremenek authored
CallExpr/ObjCMessageExpr can be visited in an "lvalue" context if it returns a struct temporary. Currently the analyzer doesn't reason about struct temporary returned by function calls, but we shouldn't crash here either. llvm-svn: 93081
-
Chris Lattner authored
llvm-svn: 93080
-
Chris Lattner authored
"In order to ease automatic bindings generation, it would be helpful if boolean values were distinguishable from integers. The attached patch introduces "typedef int LLVMBool;", and uses LLVMBool instead of int throughout the C API, wherever a boolean value is called for." Patch by James Y Knight! llvm-svn: 93079
-
Chris Lattner authored
llvm-svn: 93078
-
Chris Lattner authored
llvm-svn: 93077
-
Chris Lattner authored
llvm-svn: 93076
-
Chris Lattner authored
lvalue to poke, no functionality change. llvm-svn: 93075
-
Chris Lattner authored
llvm-svn: 93074
-
Chris Lattner authored
rdar://7083878 llvm-svn: 93073
-
Chris Lattner authored
llvm-svn: 93072
-
Ted Kremenek authored
llvm-svn: 93071
-
Jeffrey Yasskin authored
jump. People clearly weren't finding the extra requirements in CodeGenerator.html. llvm-svn: 93070
-
Chris Lattner authored
llvm-svn: 93069
-
Chris Lattner authored
llvm-svn: 93068
-
Chris Lattner authored
llvm-svn: 93067
-
Chris Lattner authored
llvm-svn: 93066
-
http://llvm.org/PR5729Jeffrey Yasskin authored
R11, and then asserting that the target was in R9. Since R9 isn't reserved for the target anymore, and is used as an argument, this patch changes the assertion. llvm-svn: 93065
-
Benjamin Kramer authored
llvm-svn: 93064
-
Chris Lattner authored
llvm-svn: 93063
-
Chris Lattner authored
llvm-svn: 93062
-
Benjamin Kramer authored
llvm-svn: 93060
-
Dan Gohman authored
so that unnamed blocks are handled. llvm-svn: 93059
-
Benjamin Kramer authored
llvm-svn: 93058
-
Benjamin Kramer authored
llvm-svn: 93057
-
Dan Gohman authored
highlighting rule for identifiers. llvm-svn: 93056
-
Dan Gohman authored
follow LLVM source convention. Before: case X: { stuff; } After: case X: { stuff; } llvm-svn: 93055
-
David Chisnall authored
Fixed linking of modules containing aliases to constant bitcasts. Existing behaviour first tried to replace the aliases with the global that they aliased (rather than the bitcast), causing a crash on an assert because the types didn't match. When this was fixed, it then did the same thing creating the new alias (creating an alias with a different type to its aliasee). Linking modules containing aliases to GEPs is still not quite right. GEPs that are equivalent to bitcasts will be replaced by bitcasts, GEPs that are not will just break. Aliases to GEPs that are not equivalent to bitcasts are horribly broken anyway (it might be worth adding an assert when creating the alias to prevent these being created; they just cause problems later). llvm-svn: 93052
-