llvm-svn: 64582

This implements gcc/testsuite/objc.dg/method-attribute-1.m

llvm-svn: 64581

creating valid LLVM structures (although they work fined).

llvm-svn: 64580

Fix pr3571: If stride is a value defined by an instruction, make sure it dominates the loop preheader. When IV users are strength reduced, the stride is inserted into the preheader. It could create a use before def situation.

llvm-svn: 64579

llvm-svn: 64578

llvm-svn: 64575

"system() declared with attribute warn_unused_result."

llvm-svn: 64574

llvm-svn: 64573

llvm-svn: 64572

Thanks Anders.

llvm-svn: 64571

starting to work for blocks.

llvm-svn: 64570

Now we are pretty close to be in sync with objc's classic 
abi when it comes to passing dejagnu objc executable tests.

llvm-svn: 64569

Warn that complex numbers are an extension in a freestanding C99
implementation.

llvm-svn: 64568

Add -ffreestanding to suppress the implicit declaration of library builtins like printf and malloc. Fixes PR3586

llvm-svn: 64566

llvm-svn: 64565

Correct two files with inconsistent lines endings.

llvm-svn: 64564

which consequently caused a Seg fault. during meta-data
generation. It also addresses an issue related to
late binding of newly synthesize ivars (when we support it).

llvm-svn: 64563

llvm-svn: 64562

about, whether they are builtins or not. Use this to add the
appropriate "format" attribute to NSLog, NSLogv, asprintf, and
vasprintf, and to translate builtin attributes (from Builtins.def)
into actual attributes on the function declaration.

Use the "printf" format attribute on function declarations to
determine whether we should do format string checking, rather than
looking at an ad hoc list of builtins and "known" function names.

Be a bit more careful about when we consider a function a "builtin" in
C++.

llvm-svn: 64561

llvm-svn: 64560

llvm-svn: 64559

ConstraintManager:
- constify getSymVal()

BasicConstraintManager:
- Pull out logic that would be common to ConstraintManagers of a similar nature
  and put them in a parent class called 'SimpleConstraintManager'.

RangeConstraintManager:
- Added a new prototype ConstraintManager to track ranges of variables! This
  ConstraintManager keeps tracks of ranges of concrete integers that a symbolic
  integer may have.

AnalysisConsumer:
- Add driver option to use RangeConstraintManager with GRExprEngine-based
  analyses.

llvm-svn: 64558

llvm-svn: 64557

llvm-svn: 64556

llvm-svn: 64555

Cleanup some warning.

Remark: when struct/class are declared differently than they are defined, this make problem for VC++ since it seems to mangle class differently that struct. These error are very hard to understand and find. So please, try to keep your definition/declaration in sync.

Only tested with VS2008. hope it does not break anything. feel free to revert.

llvm-svn: 64554

llvm-svn: 64553

intrinsics to any IntrWriteArgMem intrinsics.

llvm-svn: 64551

llvm-svn: 64550

llvm-svn: 64549

llvm-svn: 64548

llvm-svn: 64547

We don't have "zero cost" exceptions for ObjC yet, so there is no codegen
support required.

llvm-svn: 64546

llvm-svn: 64545

1) implement parser and sema support for reading and verifying attribute(warnunusedresult).
2) rename hasLocalSideEffect to isUnusedResultAWarning, inverting the sense
   of its result.
3) extend isUnusedResultAWarning to directly return the loc and range 
   info that should be reported to the user.  Make it substantially more
   precise in some cases than what was previously reported.
4) teach isUnusedResultAWarning about CallExpr to decls that are 
   pure/const/warnunusedresult, fixing a fixme.
5) change warn_attribute_wrong_decl_type to not pass in english strings, instead,
   pass in integers and use %select.

llvm-svn: 64543

llvm-svn: 64542

llvm-svn: 64541

now that this no longer implies nocapture.

llvm-svn: 64540

taken advantage of anywhere.  Change the definition
of IntrWriteArgMem to no longer imply nocapture, and
explicitly add nocapture attributes everywhere (well,
not quite everywhere, because some of these intrinsics
did capture their arguments!).  Also, make clear that
the lack of other side-effects does not exclude doing
volatile loads or stores - the atomic intrinsics do
these, yet they are all marked IntrWriteArgMem (this
change is safe because nothing exploited it).

llvm-svn: 64539

Don't ignore the const attribute - we even have CG support for that. Do ignore the malloc attribute however.

llvm-svn: 64538