| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
fix any bad objectiveC syntax coming out of
DeclPrinter. This is on going. Also, introduce a new
PrintPolicy and use it as needed when declaration tag
is to be produced via DeclPrinter.
llvm-svn: 170606
|
| |
|
|
|
|
|
| |
No testcase because this did not affect correctness: a declaration can only be
ClassTemplateDecl or a FunctionTemplateDecl, not both.
llvm-svn: 170565
|
| |
|
|
| |
llvm-svn: 170555
|
| |
|
|
|
|
| |
single attribute in the future.
llvm-svn: 170500
|
| |
|
|
| |
llvm-svn: 170487
|
| |
|
|
| |
llvm-svn: 170485
|
| |
|
|
|
|
| |
is created to 1000.
llvm-svn: 170481
|
| |
|
|
| |
llvm-svn: 170478
|
| |
|
|
|
|
|
|
|
|
|
|
| |
for plowing through macros.
This fixes a subtle bug reported in <rdar://problem/12584554> where a double-nested
macro could lead to an incorrect fixit location with live issues.
This fix also uncovers a bunch of subtle bugs in our indexer test cases which
are now fixed (mostly around source ranges for attributes).
llvm-svn: 170468
|
| |
|
|
|
|
|
|
|
|
| |
use clang's formatter. Currently, formatter is used
to format declaration tags for xml comments. Since formatter
is in flux and its change will break several of the clang comment
tests, only a single tests is formatted using this facility.
Doug has reviewed and approved it for check-in.
llvm-svn: 170467
|
| |
|
|
|
|
| |
Add OpenCL images as clang builtin types.
llvm-svn: 170432
|
| |
|
|
|
|
| |
these files to Windows style.
llvm-svn: 170431
|
| |
|
|
| |
llvm-svn: 170428
|
| |
|
|
|
|
|
|
| |
even if the directive is inside a declaration.
Fixes rdar://11548788 & http://llvm.org/PR12970
llvm-svn: 169949
|
| |
|
|
|
|
|
|
|
| |
their USR should contain a location.
This uniques them from other declarations with the same name but in different translation units.
rdar://10546541
llvm-svn: 169647
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that were already parsed in the same "indexing session".
An indexing session is defined as using the same CXIndexAction object
for multiple clang_indexSourceFile calls.
Passing CXIndexOpt_SkipParsedBodiesInSession as an indexing option will
enable the mode where we try to skip bodies that were already parsed in
another translation unit.
If a function's body was skipped, the "flags" field in the CXIdxDeclInfo
structure will have "CXIdxDeclFlag_Skipped" bit was set.
llvm-svn: 169539
|
| |
|
|
|
|
| |
Patch by Jyun-Yan You.
llvm-svn: 169276
|
| |
|
|
|
|
| |
Completely automated with sort_includes.py
llvm-svn: 169240
|
| |
|
|
|
|
| |
them to a CXString.
llvm-svn: 169227
|
| |
|
|
|
|
| |
compile commands of the database and expose it via the libclang API.
llvm-svn: 169226
|
| |
|
|
|
|
| |
No functionality change.
llvm-svn: 168738
|
| |
|
|
| |
llvm-svn: 168500
|
| |
|
|
|
|
| |
tokens at all,". This change broke External/Nurbs in LLVM test-suite.
llvm-svn: 167858
|
| |
|
|
|
|
|
|
|
| |
don't recursively continue lexing.
This avoids a stack overflow with a sequence of many empty #includes.
rdar://11988695
llvm-svn: 167801
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Thanks to Richard Smith for pointing this out. This code stopped
serving its purpose during r103212 in a refactoring. My initial
fix was to add back the logic to abort the USR generation for
InternalLinkage, but enough tests broke suspiciously that I fear
that USR generation for cursors with InternalLinkage is now expected
by some clients (where it wasn't the case when the refactoring
took place). I don't own this code anymore and have not looked
at it for some time, but clearly this code is dead and can be removed
pending further review on the proper logic here.
llvm-svn: 167442
|
| |
|
|
|
|
|
|
| |
the receiver of an ObjC message expression.
rdar://12578643
llvm-svn: 167201
|
| |
|
|
| |
llvm-svn: 166914
|
| |
|
|
| |
llvm-svn: 166913
|
| |
|
|
| |
llvm-svn: 166912
|
| |
|
|
|
|
| |
declaration.
llvm-svn: 166707
|
| |
|
|
|
|
|
| |
the various stakeholders bump up the reference count. In particular,
the diagnostics engine now keeps the DiagnosticOptions object alive.
llvm-svn: 166508
|
| |
|
|
|
|
| |
priotity, for testing
llvm-svn: 166466
|
| |
|
|
| |
llvm-svn: 166287
|
| |
|
|
|
|
|
| |
for current(rewritten) comment and getParamNameAsWritten
to access param name coming with \param marker.
llvm-svn: 166231
|
| |
|
|
| |
llvm-svn: 166163
|
| |
|
|
|
|
| |
imports.
llvm-svn: 166161
|
| |
|
|
|
|
|
|
|
|
|
| |
XML comment for declarations which pretty-prints
declaration. I had to XFAIL one test annotate-comments.cpp.
This test is currently unmaintainable as written.
Dmitri G., can you see what we can do about this test.
We should change this test such that adding a new tag does not wreck
havoc to the test.
llvm-svn: 166130
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because PNaCl bitcode must be target-independent, it uses some
different bitcode representations from other targets (e.g. byval and
sret for structures). This means that without additional type
information, it cannot meet some native ABI requirements for some
targets (e.g. passing structures containing unions by value on
x86-64). To allow generation of code which uses the correct native
ABIs, we also support triples such as x86_64-nacl, which uses
target-dependent IR (as opposed to le32-nacl, which uses byval and
sret).
To allow interoperation between the two types of code, this patch adds
a calling convention attribute to be used in code compiled with the
target-dependent triple, which will generate code using the le32-style
bitcode. This calling convention does not need to be explicitly
supported in the backend because it determines bitcode representation
rather than native conventions (the backend just needs to undersand
how to handle byval and sret for the Native Client OS).
This patch implements __attribute__((pnaclcall)) to generate calls in
bitcode according to the le32 bitcode conventions, an attribute which
is accepted by any Native Client target, but issues a warning
otherwise.
llvm-svn: 166065
|
| |
|
|
|
|
| |
of their own.
llvm-svn: 165972
|
| |
|
|
|
|
|
| |
template when comment is comming from overridden declaration.
// rdar://12378793
llvm-svn: 165953
|
| |
|
|
|
|
|
| |
has none of its own. Factor in Doug's comments.
// rdar://12378793
llvm-svn: 165771
|
| |
|
|
|
|
|
| |
Updates to llvm/Support/Casting.h have rendered these classof()'s
irrelevant.
llvm-svn: 165770
|
| |
|
|
|
|
|
|
|
| |
The ASTUnit needs to initialize an ASTWriter at the beginning of
parsing to fully handle serialization of a translation unit that
imports modules. Do this by introducing an option to enable it, which
corresponds to CXTranslationUnit_ForSerialization on the C API side.
llvm-svn: 165717
|
| |
|
|
|
|
|
|
|
|
| |
methods looking for documentation on a particular base
class inherited by any method that overrides the base class.
In case of redeclaration, as when objc method is defined
in the implementation, it also looks up for documentation
in class/class extension being redeclared.
llvm-svn: 165643
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This more accurately reflects its use: this flag is set when a method
matches the getter or setter name for a property in the same class,
and does not actually specify whether or not the definition of the method
will be synthesized (either implicitly or explicitly with @synthesize).
This renames the setter and backing field as well, and changes the
(soon-to-be-obsolete?) XML dump format to use 'property_accessor'
instead of 'synthesized'.
llvm-svn: 165626
|
| |
|
|
| |
llvm-svn: 165600
|
| |
|
|
|
|
| |
and modules are not enabled.
llvm-svn: 165593
|
| |
|
|
|
|
|
| |
an invalid location if the location points to the synthetic buffer
for the module input.
llvm-svn: 165592
|
| |
|
|
|
|
| |
This reverts commit 165429 in an attempt to get our buildbots going.
llvm-svn: 165573
|
| |
|
|
|
|
| |
ASTContext so that it can be widely available.
llvm-svn: 165473
|