Also, use SCEV to determine the trip count of the loop, which is more powerful
and accurate that Loop::getTripCount.

llvm-svn: 51179

llvm-svn: 51178

a potentially infinite loop, which is undesirable.  Instead, test the LICM behavior
that we're really interested in.

llvm-svn: 51177

llvm-svn: 51176

llvm-svn: 51173

llvm-svn: 51172

test/Verifier/2002-11-05-GetelementptrPointers.ll, which was incorrect.
Instead, fix getIndexedType to not follow pointer types, as
PointerType is a subclass of CompositeType.

llvm-svn: 51171

llvm-svn: 51170

use-before-def. The problem comes up in code with multiple PHIs where
one PHI is being rewritten in terms of the other, but the other needs
to be casted first. LLVM rules requre the cast instruction to be
inserted after any PHI instructions, but when instructions were
inserted to replace the second PHI value with a function of the first,
they were ended up going before the cast instruction. Avoid this
problem by remembering the location of the cast instruction, when one
is needed, and inserting the expansion of the new value after it.

This fixes a bug that surfaced in 255.vortex on x86-64 when
instcombine was removed from the middle of the loop optimization
passes. 

llvm-svn: 51169

in Sema::CheckFunctionCall:

  http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20080512/005706.html
  
The bug was that the logic from the helper methods used by CheckFunctionCall
were being inverted (a subtle bug).  This would cause the parser to discard
any valid AST nodes involving several builtins (see patch).

This removes the last regression failure I'm seeing in the test suite: Analysis-Apple/NoReturn.

llvm-svn: 51168

with what the test is testing; makes it pass again on ppc32.

llvm-svn: 51167

llvm-svn: 51166

llvm-svn: 51165

expressions. This appears to be a regression introduced in r51113 that caused
many test cases to fail (there is still a test case in the Analysis directory
that is failing):

http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20080512/005706.html

llvm-svn: 51164

Fix rewriter bug <rdar://problem/5929344> clang ObjC rewriter: "extern int __CFConstantStringClassReference[];" should be extern "C".

Have clang predefine OBJC_NEW_PROPERTIES (which is what gcc does).

llvm-svn: 51163

This changes the .bc file format, but if I understand
how it works correctly, old .bc files continue to
be readable.

llvm-svn: 51161

something with a v1 type.

llvm-svn: 51160

llvm-svn: 51159

Author: akirtzidis
Date: Wed May 14 05:00:15 2008
New Revision: 51101

URL: http://llvm.org/viewvc/llvm-project?rev=51101&view=rev
Log: Upgrading VC++ projects to VC++ 2008.

I really need to build with VC++ 2005.

llvm-svn: 51158

moving toward making structs and arrays first-class types.

llvm-svn: 51157

llvm-svn: 51156

llvm-svn: 51155

Patch by Matthijs Kooijman.

llvm-svn: 51154

llvm-svn: 51153

llvm-svn: 51152

llvm-svn: 51151

compiling with gcc 4.3.

llvm-svn: 51145

Fix a bunch of 80col violations that arose from the Create API change. Tweak makefile targets to find these better.

llvm-svn: 51143

llvm-svn: 51142

Make use of vector load and store operations to implement memcpy, memmove, and memset. Currently only X86 target is taking advantage of these.

llvm-svn: 51140

llvm-svn: 51139

intrin.h files are finished

llvm-svn: 51137

operator new() referring to the static initTags function, which has to be in the 
same linkage unit as any file including User.h.

llvm-svn: 51136

to 64 bits.

llvm-svn: 51135

is bitcast to return a floating point value. The result of the instruction may
not be used by the program afterwards, and LLVM will happily remove all
instructions except the call. But, on some platforms, if a value is returned as
a floating point, it may need to be removed from the stack (like x87). Thus, we
can't get rid of the bitcast even if there isn't a use of the value.

llvm-svn: 51134

llvm-svn: 51133

conversion.  Try 0x1.0000a4p+0f.  Neil, please review.

llvm-svn: 51132

llvm-svn: 51131

llvm-svn: 51130

llvm-svn: 51129