llvm-svn: 116593

Add clang_getLocationForOffset() to libclang, for gives a source location from a character index into a file.

llvm-svn: 116587

we did was an acceptable lookup. If it is, then we can re-use that
lookup result. If it isn't, we have to perform the lookup again. This
is almost surely the cause behind the mysterious typo.m failures on
some builders; we were getting the wrong lookup results returned.

llvm-svn: 116586

llvm-svn: 116577

llvm-svn: 116576

typo correction prefers "super" over other, equivalent completions. I
believe this will fix the regression on the buildbot.

llvm-svn: 116574

as the class itself. Fixes PR7082.

llvm-svn: 116573

llvm-svn: 116572

llvm-svn: 116571

llvm-svn: 116570

llvm-svn: 116569

typloc information is available (I don't think it was, originally).
Submitted as a 'trivial' change.

llvm-svn: 116568

ambiguous context.

llvm-svn: 116567

initialized. Fixes PR7076.

llvm-svn: 116553

list, complain about it! Fixes PR7053.

llvm-svn: 116551

types, from Alp Toker! Fixes PR8344.

llvm-svn: 116549

llvm-svn: 116548

This removes a lot of warnings.

llvm-svn: 116545

llvm-svn: 116544

Also, handle unknown types conservatively.

llvm-svn: 116541

its RHS is an ivar. Fixes //rdar: //8541517.

llvm-svn: 116539

This enables metadata generation by default, however the TBAA pass
in the optimizer is still disabled for now.

llvm-svn: 116536

Use root non-virtual primary base class, not just immediate primary base class, for AT_containing_type.
This is tested by virtfunc.exp in gdb testsuite.

llvm-svn: 116535

to CodeGenOption flags.

llvm-svn: 116530

llvm-svn: 116529

identifiers to determine good typo-correction candidates. Once we've
identified those candidates, we perform name lookup on each of them
and the consider the results. 

This optimization makes typo correction > 2x faster on a benchmark
example using a single typo (NSstring) in a tiny file that includes
Cocoa.h from a precompiled header, since we are deserializing far less
information now during typo correction.

There is a semantic change here, which is interesting. The presence of
a similarly-named entity that is not visible can now affect typo
correction. This is both good (you won't get weird corrections if the
thing you wanted isn't in scope) and bad (you won't get good
corrections if there is a similarly-named-but-completely-unrelated
thing). Time will tell whether it was a good choice or not.

llvm-svn: 116528

llvm-svn: 116527

llvm-svn: 116524

llvm-svn: 116522

It's more stress-free without access checking though..

llvm-svn: 116521

llvm-svn: 116519

The failing was due to this:
1. preamble.c contains CR+LF new lines
2. write() is called with a buffer containing the original (CR+LF) to output the result on the console.
3. In text mode(the default), write() convert LF to CR+LF even if LF is preceded by CR, hence we have CR+CR+LF which filecheck interprets as 2 lines.

llvm-svn: 116513

solely based on the names it sees, rather than actual declarations it
gets. In essence, we determine the set of names that are "close
enough" to the typo'd name. Then, we perform name lookup for each of
those names, filtering out those that aren't actually visible, and
typo-correct from the remaining results.

Overall, there isn't much of a change in the behavior of typo
correction here. The only test-suite change comes from the fact that
we make good on our promise to require that the user type 3 characters
for each 1 character corrected. 

The real intent behind this change is to set the stage for an
optimization to typo correction (so that we don't need to deserialize
all declarations in a translation unit) and future work in finding
missing qualification ("'vector' isn't in scope; did you mean
'std::vector'?). Plus, the code is cleaner this way.

llvm-svn: 116511

Store in PCH the key function of C++ class to avoid deserializing the complete declaration context in order to compute it.
Progress for rdar://7260160.

llvm-svn: 116508

instead of deserializing the complete declaration context of the record.

Iterating over the fields of a record is very common (e.g to determine the layout), unfortunately we needlessly deserialize every declaration
that the declaration context of the record contains; this can be bad for large C++ classes that contain a lot of methods.
Fix this by allow deserialization of just the fields when we want to iterate over them.
Progress for rdar://7260160.

llvm-svn: 116507

llvm-svn: 116506

and emits an error if a declaration with this name is deserialized from PCH.

This is for testing, to make sure that we don't deserialize stuff needlessly.

llvm-svn: 116505

Don't add the injected class name to the redeclarations chain; the chain should contain actual redeclarations, not implicits.
As a bonus, now we don't deserialize it unless we need it.

llvm-svn: 116504

Introduce command line option -dump-deserialized-decls which is used to print the PCH decls that got deserialized, for testing purposes.

llvm-svn: 116503

llvm-svn: 116493