llvm-svn: 174257

Turns out we didn't update scan-build to work with HTML files in nested directories.

llvm-svn: 174256

llvm-svn: 174255

llvm-svn: 174254

On platforms which do not support ARC natively, do not mark objc_retain/objc_release as "nonlazybind".

rdar://13108298.
rdar://13129783.

llvm-svn: 174253

llvm-svn: 174252

This reverts commit 1513eb9284c23acfd19cf742b95996fbb11ca741.

llvm-svn: 174249

Based on post-commit review by Paul Robinson.

llvm-svn: 174248

This addresses several (not all) debug info tests that use explicit metadata
numbers. Wherever the same number appeared more than once in a test I used
a named match to ensure the same number appeared in all those cases (this may
still be overly constraining test cases as they may not have actually cared
about that relationship). For one-off numbers I just replaced them with an
unnamed regex.

This may underconstrain poorly written test cases that were interested in
checking that certain metadata nodes were related but didn't actually match
on all the related nodes numbers.

llvm-svn: 174247

llvm-svn: 174246

Inlining these functions is essential for correctness. We often have
cases where we do not inline calls. For example, the shallow mode and
when reanalyzing previously inlined ObjC methods as top level.

llvm-svn: 174245

llvm-svn: 174244

llvm-svn: 174243

says, but that's a defect (to be filed). "Cls::purevfn()" is still an odr use.

Also fixes a bug that caused us to not mark the function referenced just
because we didn't want to mark it odr used.

llvm-svn: 174242

Also migrate all clients from the old API.

llvm-svn: 174238

Different modules may have different views of the various "special"
types in the AST, such as the redefinition type for "id". Merge those
types rather than only considering the redefinition types for the
first AST file loaded.

llvm-svn: 174234

llvm-svn: 174229

llvm-svn: 174218

llvm-svn: 174217

This change introduces a 'kind' attribute for the <Para> tag, that captures the
kind of the parent block command.

For example:

\todo Meow.

used to be just <Para>Meow.</Para>, but now it is
<Para kind="todo">Meow.</Para>

llvm-svn: 174216

llvm-svn: 174215

nsstringis are compared without. // rdar://12716301

llvm-svn: 174214

Suggested by Csaba. Text based on an e-mail of mine on cfe-dev.

llvm-svn: 174213

With the optimization in the previous commit, this should be safe again.

Originally applied in r173951, then reverted in r174069.

llvm-svn: 174212

This allows us to keep from chaining LazyCompoundVals in cases like this:
  CGRect r = CGRectMake(0, 0, 640, 480);
  CGRect r2 = r;
  CGRect r3 = r2;

Previously we only made this optimization if the struct did not begin with
an aggregate member, to make sure that we weren't picking up an LCV for
the first field of the struct. But since LazyCompoundVals are typed, we can
make that inference directly by comparing types.

This is a pure optimization; the test changes are to guard against possible
future regressions.

llvm-svn: 174211

r173593 made us a little too eager to associate all code at the end of a
function with the user-written 'return' line. This caused problems with
breakpoints as they'd be set in exception handling code preceeding the
actual non-exception return handling code, leading to the breakpoint never
being hit in non-exceptional execution.

This change restores the pre-r173593 exception handling line information where
the cleanup code is associated with the '}' not the return line.

llvm-svn: 174206

I've renamed the altivec test to ppc-features (because now there is more than one feature to test).

llvm-svn: 174204

Part of rdar://13134273

llvm-svn: 174203

llvm-svn: 174202

llvm-svn: 174201

llvm-svn: 174197

llvm-svn: 174195

llvm-svn: 174194

where the module was explicitly or implicitly imported in the local translation unit.

llvm-svn: 174192

module import occurred.

llvm-svn: 174191

a source location came from the predefines buffer.

llvm-svn: 174190

llvm-svn: 174185

llvm-svn: 174183

llvm-svn: 174182

Prior to the patch, Clang does not properly promote types when a complex
integer operand is combined with an integer via a binary operator, or when
one is assigned to the other in either order.  This patch detects when
promotion is needed (and permissible) and generates the necessary code.

The test assmes no target has the same size operands for "char" and
"long long," and that no target performs arithmetic on char operands without
extending them to a larger format first.  If there are any targets for
which this is not the case, they should be XFAILed.

llvm-svn: 174181