FP_REG_KILL instructions are still inserted, but can be disabled by passing
-live-x87 to llc. The X87FPRegKillInserterPass is going to be removed shortly.

CFG edges are partioned into bundles where the x87 stack must be allocated
identically. Code is insertad at the end of each basic block that shuffles the
live FP registers to match the outgoing bundles expectations.

This fix is in preparation for some upcoming register allocator improvements
that may extend the live range of registers beyond a basic block, similar to
LICM. It also provides a nice runtime speedup if you are building with
-mfpmath=387.

llvm-svn: 108529

llvm-svn: 108528

diagnostic. Instead, put it and the "declaration does not declare
anything" warning into -Wmissing-declarations.

llvm-svn: 108527

llvm-svn: 108526

llvm-svn: 108525

llvm-svn: 108524

llvm-svn: 108523

llvm-svn: 108522

purpose of access control.  Fixes PR7644.

I can't actually find anything directly justifying this, but it seems obvious.

llvm-svn: 108521

llvm-svn: 108520

llvm-svn: 108519

llvm-svn: 108518

llvm-svn: 108517

llvm-svn: 108516

This fixes PR7649.

llvm-svn: 108513

llvm-svn: 108512

llvm-svn: 108511

is well defined, it resets to the default alignment.

llvm-svn: 108508

TII::isMoveInstr is going tobe completely removed.

llvm-svn: 108507

llvm-svn: 108506

llvm-svn: 108505

llvm-svn: 108503

llvm-svn: 108502

llvm-svn: 108501

handling the parsing of scanf format strings and hooking the checking into Sema.
Most of this checking logic piggybacks on what was already there for checking printf format
strings, but the checking logic has been refactored to support both.

What is left to be done is to support argument type checking in format strings and of course
fix the usual tail of bugs that will follow.

llvm-svn: 108500

represent builtins that have the "scanf" attribution (via the format attribute) just
like we do with printf functions.  Follow-up work is needed to add similar support
for fscanf et al.

This is to support format-string checking for scanf functions.

llvm-svn: 108499

because it's more likely to keep debug line information in its original
order.

llvm-svn: 108496

the libLTO library version from the actual build version.

llvm-svn: 108495

Working on testcases for Owen.

llvm-svn: 108494

llvm-svn: 108493

llvm-svn: 108491

asm operand twice.

llvm-svn: 108489

the builtin as void __clear_cache(...) to workaround this, which appears to
match what GCC does.

llvm-svn: 108487

if the variables in that context allow a particular
JIT compiled expression to run in that context.

llvm-svn: 108485

occasions, caused code to be generated in a different order.
All cases I've seen involved float softening in the type
legalizer, and this could be perhaps be fixed there, but
it's better not to generate things differently in the first
place.  7797940 (6/29/2010..7/15/2010).

llvm-svn: 108484

llvm-svn: 108483

 - This issue here is that /usr/include/Blocks.h wants to define some of the
   block runtime globals as weak, depending on the target. This doesn't work in
   Clang because we aren't using the AST decl for these globals.

 - The fix is a pretty gross hack which just watches all the decls for the
   specific blocks globals we need to know about; if we see one we use it,
   otherwise we use the hand coded type.

   In time, I would like to clean this up by changing IRgen to ask Sema/AST for
   the decl, which would then be lazily loaded from the builtin table if
   necessary. This could be used in a whole host of places in IRgen and would
   get rid of a lot of grotty hand coding of LLVM IR; however, we need some
   extra Sema support for this as well as support for builtin global variables.

llvm-svn: 108482

llvm-svn: 108481

llvm-svn: 108480

llvm-svn: 108478