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).
70 lines
2.5 KiB
C++
70 lines
2.5 KiB
C++
//===- MachineDomTreeUpdater.cpp -----------------------------------------===//
|
|
//
|
|
// 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
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
//
|
|
// This file implements the MachineDomTreeUpdater class, which provides a
|
|
// uniform way to update dominator tree related data structures.
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "llvm/CodeGen/MachineDomTreeUpdater.h"
|
|
#include "llvm/Analysis/GenericDomTreeUpdaterImpl.h"
|
|
#include "llvm/CodeGen/MachinePostDominators.h"
|
|
#include "llvm/Support/Compiler.h"
|
|
|
|
namespace llvm {
|
|
|
|
template class LLVM_EXPORT_TEMPLATE GenericDomTreeUpdater<
|
|
MachineDomTreeUpdater, MachineDominatorTree, MachinePostDominatorTree>;
|
|
|
|
template LLVM_EXPORT_TEMPLATE void
|
|
GenericDomTreeUpdater<MachineDomTreeUpdater, MachineDominatorTree,
|
|
MachinePostDominatorTree>::recalculate(MachineFunction
|
|
&MF);
|
|
|
|
template LLVM_EXPORT_TEMPLATE void GenericDomTreeUpdater<
|
|
MachineDomTreeUpdater, MachineDominatorTree,
|
|
MachinePostDominatorTree>::applyUpdatesImpl</*IsForward=*/true>();
|
|
template LLVM_EXPORT_TEMPLATE void GenericDomTreeUpdater<
|
|
MachineDomTreeUpdater, MachineDominatorTree,
|
|
MachinePostDominatorTree>::applyUpdatesImpl</*IsForward=*/false>();
|
|
|
|
bool MachineDomTreeUpdater::forceFlushDeletedBB() {
|
|
if (DeletedBBs.empty())
|
|
return false;
|
|
|
|
for (auto *BB : DeletedBBs) {
|
|
eraseDelBBNode(BB);
|
|
BB->eraseFromParent();
|
|
}
|
|
DeletedBBs.clear();
|
|
return true;
|
|
}
|
|
|
|
// The DT and PDT require the nodes related to updates
|
|
// are not deleted when update functions are called.
|
|
// So MachineBasicBlock deletions must be pended when the
|
|
// UpdateStrategy is Lazy. When the UpdateStrategy is
|
|
// Eager, the MachineBasicBlock will be deleted immediately.
|
|
void MachineDomTreeUpdater::deleteBB(MachineBasicBlock *DelBB) {
|
|
validateDeleteBB(DelBB);
|
|
if (Strategy == UpdateStrategy::Lazy) {
|
|
DeletedBBs.insert(DelBB);
|
|
return;
|
|
}
|
|
|
|
eraseDelBBNode(DelBB);
|
|
DelBB->eraseFromParent();
|
|
}
|
|
|
|
void MachineDomTreeUpdater::validateDeleteBB(MachineBasicBlock *DelBB) {
|
|
assert(DelBB && "Invalid push_back of nullptr DelBB.");
|
|
assert(DelBB->pred_empty() && "DelBB has one or more predecessors.");
|
|
}
|
|
|
|
} // namespace llvm
|