| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
been fixed since r206644.
llvm-svn: 206685
|
|
|
|
|
|
| |
This has been failing since r206202.
llvm-svn: 206294
|
|
|
|
|
|
|
| |
This is at least good documentation, but also opens the possibility of
using pipefail.
llvm-svn: 185652
|
|
|
|
|
|
|
|
| |
that does not exist.
rdar://11607033
llvm-svn: 158193
|
|
|
|
|
|
|
|
| |
invalid ParmVarDecls.
Part of rdar://11007039.
llvm-svn: 152437
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an error made a record member invalid, the record would stay as "isBeingDefined" and
not "completeDefinition". Even easily recoverable errors ended up propagating records in
such "beingDefined" state, for example:
struct A {
~A() const; // expected-error {{'const' qualifier is not allowed on a destructor}}
};
struct B : A {}; // A & B would stay as "not complete definition" and "being defined".
This weird state was impending lookups in the records and hitting assertion in the ASTWriter.
Part of rdar://11007039
llvm-svn: 152432
|
|
|
|
|
|
|
|
| |
an #include entry that did not resolve to header file.
Part of rdar://11007039
llvm-svn: 152275
|
|
compiler errors or not.
-Control whether ASTReader should reject such a PCH by a boolean flag at ASTReader's creation time.
By default, such a PCH file will be rejected with an error when trying to load it.
[libclang] Allow clang_saveTranslationUnit to create a PCH file even if compiler errors
occurred.
-Have libclang API calls accept a PCH that had compiler errors.
The general idea is that we want libclang to stay functional even if a PCH had a compiler error.
rdar://10976363.
llvm-svn: 152192
|