When an instruction has tied operands and physreg defines, we must take extra
care that the tied operands conflict with neither physreg defs nor uses.

The special treatment is given to inline asm and instructions with tied operands
/ early clobbers and physreg defines.

This fixes PR7509.

llvm-svn: 107043

llvm-svn: 107042

llvm-svn: 107040

Remove library check and regenerate configure.

llvm-svn: 107028

Radar 8122864.

llvm-svn: 107027

llvm-svn: 107025

llvm-svn: 107024

llvm-svn: 107022

llvm-svn: 107021

I broke negate of FP values.

llvm-svn: 107019

llvm-svn: 107018

llvm-svn: 107017

llvm-svn: 107016

llvm-svn: 107015

llvm-svn: 107014

interprocedurally. Note that as of this writing, existing alias
analysis passes are not prepared to be used interprocedurally.

llvm-svn: 107013

llvm-svn: 107012

name, specifically the "lib" prefix.

llvm-svn: 107011

block, not...", it caused a bunch of nightly test regressions.

llvm-svn: 107009

we ignoring before.  To give access to the names on the initializer,
which aren't a type or an expr or a decl, I've introduced a new
TraverseInitializer.  By default, it just traverses on the expr that
the name is being initialized to.

Reviewed by chandlerc.  Tested via clang's 'make test'.

llvm-svn: 107008

Introduce Expr::Classify and Expr::ClassifyModifiable, which determine the classification of an expression under the C++0x taxology (value category). Reimplement isLvalue and isModifiableLvalue using these functions. No regressions in the test suite from this, and my rough performance check doesn't show any regressions either.

llvm-svn: 107007

llvm-svn: 107004

llvm-svn: 107003

llvm-svn: 107002

(in both CallInst and InvokeInst)

also add a (short-lived) constant to CallInst, that names
the operand index of the first call argument. This is
strictly transitional and should not be used for new code.

llvm-svn: 107001

llvm-svn: 107000

llvm-svn: 106999

llvm-svn: 106998

llvm-svn: 106997

llvm-svn: 106996

llvm-svn: 106995

This is more targeted, as it simply provides toggle actions for the parser to
turn access checking on and off. We then use these to suppress access checking
only while we parse the template-id (included scope specifier) of an explicit
instantiation and explicit specialization of a class template. The
specialization behavior is an extension, as it seems likely a defect that the
standard did not exempt them as it does explicit instantiations.

This allows the very common practice of specializing trait classes to work for
private, internal types. This doesn't address instantiating or specializing
function templates, although those apparently already partially work.

The naming and style for the Action layer isn't my favorite, comments and
suggestions would be appreciated there.

llvm-svn: 106993

Pointer comparisons (and pointer-pointer subtraction). Basically filling in SimpleSValuator::EvalBinOpLL().

llvm-svn: 106992

llvm-svn: 106990

Use named MDNode, llvm.dbg.sp, to collect subprogram info. This will be used to emit  local variable's debug info of deleted functions.

llvm-svn: 106989

llvm-svn: 106988

much as we already do for allocation function lookup. Explicitly check access
for the function we actually select in one case that was previously missing,
but being caught behind the blanket diagnostics for all overload candidates.
This fixs PR7436.

llvm-svn: 106986

Do not forget last element, function, while creating Subprogram definition MDNode from subprogram declare MDNode.

llvm-svn: 106985

llvm-svn: 106984

Correctly destroy reference temporaries with global storage. Remove ErrorUnsupported call when binding a global reference to a non-lvalue. Fixes PR7326.

llvm-svn: 106983