llvm-svn: 64473

llvm-svn: 64472

llvm-svn: 64471

implementation with no category declaration!

llvm-svn: 64470

 - Now at 1274 passes on gcc compat suite vs 1262.

llvm-svn: 64469

printing getName(), so that unnamed values are printed correctly.

llvm-svn: 64468

llvm-svn: 64467

llvm-svn: 64466

about the code it describes, but at least now the comment
is right.

llvm-svn: 64465

being used for atomic intrinsics, it seems the
access may be volatile.  No code was exploiting
the original non-volatile definition, so only
the comment needs changing.

llvm-svn: 64464

it only reads memory!  The other change has no
functional effect, it just seems more logical to
go in order of decreasing knowledge.

llvm-svn: 64463

llvm-svn: 64461

llvm-svn: 64460

llvm-svn: 64459

llvm-svn: 64458

llvm-svn: 64457

llvm-svn: 64456

llvm-svn: 64455

llvm-svn: 64454

mark the first argument nocapture if endptr=NULL for each particular call.

llvm-svn: 64453

llvm-svn: 64452

llvm-svn: 64451

llvm-svn: 64450

link-time failures when building with optimization.  Just
get rid of them.

llvm-svn: 64449

llvm-svn: 64448

llvm-svn: 64447

llvm-svn: 64446

llvm-svn: 64445

llvm-svn: 64444

Make sure the SCC pass manager initializes any contained
function pass managers.  Without this, simplify-libcalls
would add nocapture attributes when run on its own, but
not when run as part of -std-compile-opts or similar.

llvm-svn: 64443

couldn't ever be the return of call instruction. However, it's quite possible
that said local allocation is itself the return of a function call. That's
what malloc and calloc are for, actually.

llvm-svn: 64442

llvm-svn: 64441

addrec in a different loop to check the value being added to
the accumulated Start value, not the Start value before it has
the new value added to it. This prevents LSR from going crazy
on the included testcase. Dale, please review.

llvm-svn: 64440

"I got blisters on my fingers."

llvm-svn: 64439

llvm-svn: 64438

There were some that might even matter in X86FastISel.

llvm-svn: 64437

llvm-svn: 64436

llvm-svn: 64435

Currently only used for 128-bit integers.

Note that we can't use the fixed-width integer types for other integer 
modes without other changes because glibc headers redefines (u)int*_t 
and friends using the mode attribute.  For example, this means that uint64_t
has to be compatible with unsigned __attribute((mode(DI))), and 
uint64_t is currently defined to long long.  And I have a feeling we'll 
run into issues if we try to define uint64_t as something which isn't 
either long or long long.

This doesn't get the alignment right in most cases, including 
the 128-bit integer case; I'll file a PR shortly.  The gist of the issue 
is that the targets don't really expose the information necessary to 
figure out the alignment outside of the target description, so there's a 
non-trivial amount of work involved in getting it working right.  That 
said, the alignment used is conservative, so the only issue with the 
current implementation is ABI compatibility.

This makes it trivial to add some sort of "bitwidth" attribute to make 
arbitrary-width integers; I'll do that in a followup.

We could also use this for stuff like the following for compatibility 
with gcc, but I have a feeling it would be a better idea for clang to be 
consistent between C and C++ modes rather than follow gcc's example for 
C mode.
struct {unsigned long long x : 33;} x;
unsigned long long a(void) {return x.x+1;}

llvm-svn: 64434

llvm-svn: 64433