llvm-svn: 60363

__ASSEMBLER__ properly. Patch from Roman Divacky (with minor
formatting changes). Thanks!

llvm-svn: 60362

llvm-svn: 60361

llvm-svn: 60360

llvm-svn: 60359

llvm-svn: 60357

llvm-svn: 60355

llvm-svn: 60334

llvm-svn: 60333

llvm-svn: 60331

llvm-svn: 60324

llvm-svn: 60323

llvm-svn: 60321

llvm-svn: 60320

Add Sema::isNullPointerConstant which extwarns if necessary. Use it in Sema::CheckConditionalOperands.

llvm-svn: 60319

llvm-svn: 60318

llvm-svn: 60317

llvm-svn: 60316

llvm-svn: 60305

llvm-svn: 60301

llvm-svn: 60300

llvm-svn: 60299

llvm-svn: 60298

llvm-svn: 60297

llvm-svn: 60296

llvm-svn: 60295

llvm-svn: 60282

llvm-svn: 60281

This fixes PR3127
http://llvm.org/bugs/show_bug.cgi?id=3127

llvm-svn: 60280

initializers.  llvm-gcc appears to be more aggressive, but incorrect, 
for constructs like "const int a[] = {1,2,3};"; that said, current 
optimizers will do the appropriate optimizations when safe.

llvm-svn: 60270

llvm-svn: 60269

llvm-svn: 60249

llvm-svn: 60248

llvm-svn: 60235

bitmangling.

llvm-svn: 60226

When initialized, the index of the ElementRegion was unsigned. But the index
value of the ArraySubscriptExpr is signed. This inconsistency caused the value
of the array element retrieved to be UnknownVal despite it was initialized to
symbolic.

This is only a hack. Real fix of this problem is required.

llvm-svn: 60207

llvm-svn: 60206

llvm-svn: 60205

the ConstraintManager can print its internal state before its solver instance is
destroyed.

llvm-svn: 60204

llvm-svn: 60181