Lines Matching refs:Diagnose
120 // Try to diagnose why this special member function was implicitly
124 ShouldDeleteSpecialMember(Method, CSM, /*Diagnose=*/true);
589 // Nothing to diagnose. This is okay.
1351 /// Diagnose an empty lookup.
1672 // call, diagnose the problem.
1827 // Diagnose using an ivar in a class method.
1841 // Diagnose the use of an ivar outside of the declaring class.
2195 // Specifically diagnose references to class templates that are missing
3237 // Diagnose bad cases where we step over interface counts.
5711 bool Diagnose) {
5718 if (Diagnose) {
5987 /// \brief Diagnose invalid arithmetic on two void pointers.
5997 /// \brief Diagnose invalid arithmetic on a void pointer.
6006 /// \brief Diagnose invalid arithmetic on two function pointers.
6022 /// \brief Diagnose invalid arithmetic on a function pointer.
6082 /// This routine will diagnose any invalid arithmetic on pointer operands much
6206 // Diagnose "string literal" '+' int.
6237 // Diagnose bad cases where we step over interface counts.
6293 // Diagnose bad cases where we step over interface counts.
6496 /// \brief Diagnose bad pointer comparisons.
7053 // Diagnose cases where the user write a logical and/or but probably meant a
7449 // Diagnose bad cases where we step over interface counts.
7551 /// \brief Diagnose invalid operand for address of operations.
8043 // Don't diagnose this.
8166 // Diagnose "arg1 'bitwise' arg2 'eq' arg3".
8170 // Diagnose "arg1 & arg2 | arg3"
8677 // GCC extension, diagnose them.
8773 // We diagnose this as an error.
9107 // If needed, diagnose invalid gotos and switches in the block.
9365 // FIXME: Diagnose the problem in ObjCQualifiedIdTypesAreCompatible, since
9856 // For C code, don't diagnose about capture if we're not actually in code
9993 if (!Init.Diagnose(S, Entities.back(), InitKind, &Ref, 1))
10665 // Diagnose the s/=/==/ and s/\|=/!=/ typos. Note that adding parentheses
