vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
27 lines
947 B
C++
27 lines
947 B
C++
// RUN: %clang_cc1 -verify %s
|
|
// RUN: %clang_cc1 -verify %s -std=c++98
|
|
// RUN: %clang_cc1 -verify %s -std=c++11
|
|
// RUN: %clang_cc1 -verify %s -std=c++1z
|
|
|
|
// PR25946
|
|
// We had an off-by-one error in an assertion when annotating A<int> below. Our
|
|
// error recovery checks if A<int> is a constructor declarator, and opens a
|
|
// TentativeParsingAction. Then we attempt to annotate the token at the exact
|
|
// position that we want to possibly backtrack to, and this used to crash.
|
|
|
|
template <typename T> class A {};
|
|
|
|
// expected-error@+1 {{expected '{' after base class list}}
|
|
template <typename T> class B : T // not ',' or '{'
|
|
#if __cplusplus < 201103L
|
|
// expected-error@+8 {{expected ';' after top level declarator}}
|
|
#endif
|
|
#if __cplusplus <= 201402L
|
|
// expected-error@+5 {{a type specifier is required for all declarations}}
|
|
#else
|
|
// expected-error@+3 {{expected unqualified-id}}
|
|
#endif
|
|
// expected-error@+1 {{expected ';' after class}}
|
|
A<int> {
|
|
};
|