- Apr 14, 2010
-
-
Dan Gohman authored
llvm-svn: 101264
-
Dan Gohman authored
llvm-svn: 101263
-
Dan Gohman authored
don't need it. llvm-svn: 101262
-
Dan Gohman authored
drop the redundant #ifndef NDEBUG. llvm-svn: 101261
-
Dan Gohman authored
llvm-svn: 101260
-
Douglas Gregor authored
than just a bool indicating that correction occurred. No actual functionality change (it's still always used like a bool), but this refactoring will be used to support typo correction to keywords. llvm-svn: 101259
-
Dan Gohman authored
SelectionDAGISel. llvm-svn: 101258
-
Daniel Dunbar authored
IRgen record layout, which this code doesn't need to depend on. llvm-svn: 101257
-
Dan Gohman authored
llvm-svn: 101256
-
Dan Gohman authored
llvm-svn: 101255
-
Dan Gohman authored
llvm-svn: 101254
-
Gabor Greif authored
llvm-svn: 101253
-
Dan Gohman authored
SelectionDAGISel::runOnMachineFunction into FunctionLowering. llvm-svn: 101252
-
Dan Gohman authored
llvm-svn: 101251
-
Gabor Greif authored
llvm-svn: 101250
-
Douglas Gregor authored
that adds parentheses from the main diagnostic down to a new note. This way, when the fix-it represents a choice between two options, each of the options is associted with a note. There is no default option in such cases. For example: /Users/dgregor/t.c:2:9: warning: & has lower precedence than ==; == will be evaluated first [-Wparentheses] if (x & y == 0) { ^~~~~~~~ /Users/dgregor/t.c:2:9: note: place parentheses around the & expression to evaluate it first if (x & y == 0) { ^ ( ) /Users/dgregor/t.c:2:9: note: place parentheses around the == expression to silence this warning if (x & y == 0) { ^ ( ) llvm-svn: 101249
-
Dan Gohman authored
llvm-svn: 101248
-
Dan Gohman authored
llvm-svn: 101247
-
Dan Gohman authored
llvm-svn: 101246
-
Dan Gohman authored
llvm-svn: 101245
-
Dan Gohman authored
llvm-svn: 101244
-
Dan Gohman authored
llvm-svn: 101243
-
Benjamin Kramer authored
llvm-svn: 101241
-
Zhongxing Xu authored
llvm-svn: 101239
-
Zhongxing Xu authored
llvm-svn: 101238
-
Nick Lewycky authored
incompatibility with some clients covered by the buildbots, such as llvm-gcc. llvm-svn: 101237
-
Zhongxing Xu authored
llvm-svn: 101236
-
Daniel Dunbar authored
Speculatively revert "IRgen: Move EmitStoreThroughBitfieldLValue to use new CGBitfieldInfo::AccessInfo decomposition, instead of computing the access policy itself.", I think it might be breaking bootstrap. llvm-svn: 101235
-
Nick Lewycky authored
llvm-svn: 101234
-
Nick Lewycky authored
llvm-svn: 101233
-
Nick Lewycky authored
have been removed in r101231. llvm-svn: 101232
-
Nick Lewycky authored
llvm-svn: 101231
-
Nick Lewycky authored
llvm-svn: 101230
-
Nick Lewycky authored
llvm-svn: 101229
-
Nick Lewycky authored
llvm-svn: 101228
-
Chris Lattner authored
current PC. rdar://7834775 We now produce an identical .o file compared to the cctools assembler for something like this: _f0: L0: jmp L1 .long . - L0 L1: jmp A .long . - L1 .zerofill __DATA,_bss,A,0 llvm-svn: 101227
-
Chris Lattner authored
llvm-svn: 101226
-
Chris Lattner authored
llvm-svn: 101224
-
Nick Lewycky authored
llvm-svn: 101223
-
Daniel Dunbar authored
IRgen: Move EmitStoreThroughBitfieldLValue to use new CGBitfieldInfo::AccessInfo decomposition, instead of computing the access policy itself. - Sadly, this doesn't seem to give any .ll size win so far. It is possible to make this routine significantly smarter & avoid various shifting, masking, and zext/sext, but I'm not really convinced it is worth it. It is tricky, and this is really instcombine's job. - No intended functionality change; the test case is just to increase coverage & serves as a demo file, it worked before this commit. llvm-svn: 101222
-