Also rename ABSTRACT to ABSTRACT_STMT

llvm-svn: 104018

Also rename ABSTRACT to ABSTRACT_STMT, in keeping with the other .def
files

llvm-svn: 104017

for Visual Studio 2010.  It also adds a registry search
for the Express edition,", from Steven Watanabe!

llvm-svn: 104015

Revert much of the implementation of C++98/03 [temp.friend]p5 in
r103943 and its follow-ons r103948 and r103952. While our
implementation was technically correct, other compilers don't seem to
implement this paragraph (which forces the instantiation of friend
functions defined in a class template when a class template
specialization is instantiated), and doing so broke a bunch of Boost
libraries. 

Since this behavior has changed in C++0x (which instantiates the
friend function definitions when they are used), we're going to skip
the nowhere-implemented C++98/03 semantics and go straight to the
C++0x semantics.

This commit is a band-aid to get Boost up and running again. It
doesn't really fix PR6952 (which this commit un-fixes), but it does
deal with the way Boost.Units abuses this particular paragraph.

llvm-svn: 104014

llvm-svn: 104013

Start laying out bases as individual fields. We still use ugly i8 arrays but this is a step in the right direction.

llvm-svn: 104012

llvm-svn: 104011

If a switch condition is constant, warn if there's no case for it.

Constant switch conditions do come up in reasonable template code.

llvm-svn: 104010

llvm-svn: 104008

number of times the analyzer will go through a loop.

llvm-svn: 104007

llvm-svn: 104006

llvm-svn: 104005

FIX PR7158. SimplifyVBinOp was asserting when it fails to constant fold (op (build_vector), (build_vector)). 

llvm-svn: 104004

llvm-svn: 104001

a temporary with a noreturn destructor has been created. Fixes PR6884 for now.

llvm-svn: 104000

when we really need a proper audit of our handling of attributes in
templates.

llvm-svn: 103999

too large limit.

The function would return immediately when finding an addrmode 3/5 instruction.
It needs to keep scanning in case there is an addrmode 6 instruction which drops
the limit to 0.

A test case is very difficult to produce because it will only fail when the
scavenger is used.

rdar://problem/7894847

llvm-svn: 103995

Fix PR7175. Insert copies of a REG_SEQUENCE source if it is used by other REG_SEQUENCE instructions.

llvm-svn: 103994

how you're supposed to use it.

llvm-svn: 103993

- Change the logic DisableFramePointerElim() to check for the
  -disable-non-leaf-fp-elim before -disable-fp-elim.

llvm-svn: 103990

llvm-svn: 103989

cases where Clang can suggest and fix and suggest and not auto-fix (because of
current limitations).

llvm-svn: 103987

llvm-svn: 103986

and cleanup comments as well.

llvm-svn: 103985

Fix PR7156. If the sources of a REG_SEQUENCE are all IMPLICIT_DEF's. Replace it with an IMPLICIT_DEF rather than deleting it or else it would be left without a def.

llvm-svn: 103984

[rand.dist.norm.cauchy].  I'm having trouble testing the output as all statistical properties are undefined.  They do not converge upon any one value as the number of samples increases.  Suggestions for tests welcome.

llvm-svn: 103983

llvm-svn: 103982

MC/Mach-O/x86: Optimal nop sequences should only be used for the .text sections, not all sections in the text segment.

llvm-svn: 103981

 - Of questionable utility, since in general anything which wants to do this should probably be within a target specific hook, which can rely on the sections being of the appropriate type. However, it can be useful for short term hacks.

llvm-svn: 103980

 - This fixes a string table mismatch with 'as' when two new symbols are defined
   in a single instruction.

llvm-svn: 103979

This fixes the miscompilations of MultiSource/Applications/JM/l{en,de}cod.
Clang now successfully self hosts in a debug build with the fast register allocator.

llvm-svn: 103975

llvm-svn: 103974

out.  The remaining ones are okay.

llvm-svn: 103973

llvm-svn: 103972

llvm-svn: 103971

llvm-svn: 103970

Obvious in retrospect but not fun to debug.

llvm-svn: 103969

make it miss (invalid) things like:
<<<<<<<
>>>>>>>

and crash if 

<<<<<<< 

was at the end of the line.  When we find a >>>>>>> that is not at the
end of the line, make sure to reset Pos so we don't crash on something
like:
<<<<<<< >>>>>>>

This isn't worth making testcases for, since each would require a new file.

rdar://7987078 - signal 11 compiling "<<<<<<<<<<"

llvm-svn: 103968

llvm-svn: 103966

Fixes rdar://problem/7992749

llvm-svn: 103965