llvm-svn: 174007

llvm-svn: 174006

llvm-svn: 174005

Several places were still treating the Attribute object as respresenting
multiple attributes. Those places now use the AttributeSet to represent
multiple attributes.

llvm-svn: 174004

Several places were still treating the Attribute object as respresenting
multiple attributes. Those places now use the AttributeSet to represent
multiple attributes.

llvm-svn: 174003

llvm-svn: 174002

llvm-svn: 174001

llvm-svn: 174000

llvm-svn: 173999

with an assert instead of failing and requiring callers to check for failure.

llvm-svn: 173998

llvm-svn: 173997

llvm-svn: 173996

for example, a one-past-the-end pointer from one global variable may
be equal to the base pointer of another global variable.

llvm-svn: 173995

As a bonus I put in some extra checks to make sure that we are identifying the
machine word of various Mac OS X/iOS targets appropriately.

llvm-svn: 173994

On systems which support the QPX vector instructions, the stack must be
32-byte aligned.

llvm-svn: 173993

llvm-svn: 173992

  #define X X

for which there is no point warning, ever.

llvm-svn: 173991

There are still places which treat the Attribute object as a collection of
attributes. I'm systematically removing them.

llvm-svn: 173990

C++11 lambdas that don't capture anything can be used as static callback functions!

Heavily modified this python module to be able to not require a dylib in order to traverse the heap allocations.

Re-implemented the ptr_refs, objc_refs, malloc_info and cstr_refs to use complex expressions that use lambdas to do all static callback function work.

llvm-svn: 173989

llvm-svn: 173988

llvm-svn: 173987

llvm-svn: 173986

What I thought was going to be a quick thing has extended out a little bit in
time *sigh*. So after some thought in order to not cruft up the tree I am
removing this for now since it is the right thing to do.

llvm-svn: 173985

This should have gone in with r173973.

llvm-svn: 173984

so we follow the convention that all other platforms follow by having an is*
test method.

llvm-svn: 173983

setting is working correctly now; remove the #if 0's around its
use.

llvm-svn: 173982

Thanks, Sean.

llvm-svn: 173981

llvm-svn: 173980

file contents being autogenerated

llvm-svn: 173979

llvm-svn: 173978

 - I got confused by the double negative, the test succends on 10.6, in which
   case we *do* want to perform the filter-out.

llvm-svn: 173977

Specifically, don't print snippets, caret diagnostics, or ranges for
lines over 4096 characters. We copy the line around a few times in our
diagnostics machinery, and we have to print a caret line that's just as
long. This uses a lot of memory just to create a poor user experience as
we print out a line much too long for anyone to read...or spend extra
energy trying to fit it to -fmessage-length.

<rdar://problem/13106850>

llvm-svn: 173976

It was creating a new AttrBuilder when we could just fill in the AttrBuilder
we're building.

llvm-svn: 173975

prevent an llvm developer from mistakenly thinking that just because the
intrinsic has volatile flags that volatile operations can be converted
to or folded into them.

Platforms may rely on volatile loads and stores of natively supported
data width to be executed as single instruction. When compiling
C, this expectation likely holds for l-values of volatile primitive
types with native hardware support, but not necessarily for aggregate
types. The frontend upholds these expectations, which are not
specified in the IR.

llvm-svn: 173974

This is the first commit of a large series which will add support for the
QPX vector instruction set to the PowerPC backend. This instruction set is
used on the IBM Blue Gene/Q supercomputers.

llvm-svn: 173973

llvm-svn: 173971

This reverts commit r173952

llvm-svn: 173970

Boilerplate is often the hardest part of getting started with these
kinds of things, so throw them a bone.

llvm-svn: 173969

llvm-svn: 173968

llvm-svn: 173966