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).
35 lines
1.7 KiB
C++
35 lines
1.7 KiB
C++
//===- TemplateArgumentHasher.h - Hash Template Arguments -------*- C++ -*-===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "clang/AST/TemplateBase.h"
|
|
|
|
namespace clang {
|
|
namespace serialization {
|
|
|
|
/// Calculate a stable hash value for template arguments. We guarantee that
|
|
/// the same template arguments must have the same hashed values. But we don't
|
|
/// guarantee that the template arguments with the same hashed value are the
|
|
/// same template arguments.
|
|
///
|
|
/// ODR hashing may not be the best mechanism to hash the template
|
|
/// arguments. ODR hashing is (or perhaps, should be) about determining whether
|
|
/// two things are spelled the same way and have the same meaning (as required
|
|
/// by the C++ ODR), whereas what we want here is whether they have the same
|
|
/// meaning regardless of spelling. Maybe we can get away with reusing ODR
|
|
/// hashing anyway, on the basis that any canonical, non-dependent template
|
|
/// argument should have the same (invented) spelling in every translation
|
|
/// unit, but it is not sure that's true in all cases. There may still be cases
|
|
/// where the canonical type includes some aspect of "whatever we saw first",
|
|
/// in which case the ODR hash can differ across translation units for
|
|
/// non-dependent, canonical template arguments that are spelled differently
|
|
/// but have the same meaning. But it is not easy to raise examples.
|
|
unsigned StableHashForTemplateArguments(llvm::ArrayRef<TemplateArgument> Args);
|
|
|
|
} // namespace serialization
|
|
} // namespace clang
|