ValueObjects when creating variables referring to
live data rather than constructing
ValueObjectConstResults.

llvm-svn: 145437

we infer the module map, we'll just print the module map to a
temporary file and generate the module using that.

llvm-svn: 145436

llvm-svn: 145435

llvm-svn: 145434

implementation of the linux platform.

llvm-svn: 145433

Potential bug in RewriteLoopBodyWithConditionConstant: use iterator should not be changed inside the uses enumeration loop.

llvm-svn: 145432

multiple .a files would end up with duplicate strong definitions. This could
cause link failures in certain scenarios when both definitions got loaded.
 - The best solution I see for this (aside from not factoring out the utility
   code) is to mark the definitions weak. Better solutions appreciated!

llvm-svn: 145427

be more clear about what to do and how to do it.

llvm-svn: 145426

attempt.  

llvm-svn: 145425

Relax RegionStore to allow loads from CodeTextRegions.  Apparently you can actually write code that does this.  This seems worthy of a checker, but the StoreManager should handle the memory abstraction without crashing.  Fixes PR 11450.

llvm-svn: 145424

llvm-svn: 145423

llvm-svn: 145422

llvm-svn: 145421

llvm-svn: 145420

llvm-svn: 145419

llvm-svn: 145418

llvm-svn: 145417

Patch by Sanjoy Das.

llvm-svn: 145416

module map, rather than assuming that there is an umbrella
header. This allows us to automatically build umbrella-less modules. 

llvm-svn: 145415

on-the-fly. No functionality change.

llvm-svn: 145414

weak variable are compiled by different compilers, such as GCC and LLVM, while
LLVM may increase the alignment to the preferred alignment there is no reason to
think that GCC will use anything more than the ABI alignment.  Since it is the
GCC version that might end up in the final program (as the linkage is weak), it
is wrong to increase the alignment of loads from the global up to the preferred
alignment as the alignment might only be the ABI alignment.

Increasing alignment up to the ABI alignment might be OK, but I'm not totally
convinced that it is.  It seems better to just leave the alignment of weak
globals alone.

llvm-svn: 145413

llvm-svn: 145412

interface. No functionality change.

llvm-svn: 145411

llvm-svn: 145410

as MC is the only assembler we support.

This splits MS/Windows and GNU/Windows ASM infos into two seperate classes.
While there is currently only one difference, full MS C++ ABI support will
require many more.

llvm-svn: 145409

- getSymbolOffset() renamed as getSymbolFileOffset()
- getSymbolFileOffset(), getSymbolAddress(), getRelocationAddress() returns same result for ELFObjectFile, MachOObjectFile and COFFObjectFile.
- added getRelocationOffset()
- fixed MachOObjectFile::getSymbolSize()
- fixed MachOObjectFile::getSymbolSection()
- fixed MachOObjectFile::getSymbolOffset() for symbols without section data.

llvm-svn: 145408

llvm-svn: 145407

Added a test.
Thanks Bruno for reviewing the patch.

llvm-svn: 145403

This fixes the test with recent versions of LLVM that do not support
the old atomic instructions any more.

llvm-svn: 145402

This tool takes a jscop file and translates it into a cloog input file.

llvm-svn: 145401

llvm-svn: 145400

llvm-svn: 145399

llvm-svn: 145397

llvm-svn: 145396

was probably meant to be 'typename', which we will have already suggested if it
is appropriate.

llvm-svn: 145395

for late parsing.

llvm-svn: 145394

llvm-svn: 145393

llvm-svn: 145392

Fix issues in shuffle decoding around VPERM* instructions. Fix shuffle decoding for VSHUFPS/D for 256-bit types. Add pattern matching for memory forms of VPERMILPS/VPERMILPD.

llvm-svn: 145390

clang/lib/Driver/Driver.cpp: Don't pass through negative exit status, or parent would be confused.

llvm::sys::Program::Wait(): Suppose 0x8000XXXX and 0xC000XXXX as abnormal exit code and pass it as negative value.

Win32 Exception Handler: Exit with ExceptionCode on an unhandle exception.

llvm-svn: 145389