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).
69 lines
2.3 KiB
Plaintext
69 lines
2.3 KiB
Plaintext
// REQUIRES: x86-registered-target
|
|
// REQUIRES: nvptx-registered-target
|
|
|
|
// Make sure we don't emit vtables for classes with methods that have
|
|
// inappropriate target attributes. Currently it's mostly needed in
|
|
// order to avoid emitting vtables for host-only classes on device
|
|
// side where we can't codegen them.
|
|
|
|
// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -emit-llvm -o - %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-HOST -check-prefix=CHECK-BOTH
|
|
// RUN: %clang_cc1 -triple nvptx64-nvidia-cuda -fcuda-is-device -emit-llvm -o - %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-DEVICE -check-prefix=CHECK-BOTH
|
|
|
|
#include "Inputs/cuda.h"
|
|
|
|
struct H {
|
|
virtual void method();
|
|
};
|
|
//CHECK-HOST: @_ZTV1H =
|
|
//CHECK-HOST-SAME: @_ZN1H6methodEv
|
|
//CHECK-DEVICE-NOT: @_ZTV1H =
|
|
//CHECK-DEVICE-NOT: @_ZTVN10__cxxabiv117__class_type_infoE
|
|
//CHECK-DEVICE-NOT: @_ZTS1H
|
|
//CHECK-DEVICE-NOT: @_ZTI1H
|
|
struct D {
|
|
__device__ virtual void method();
|
|
};
|
|
|
|
//CHECK-DEVICE: @_ZTV1D
|
|
//CHECK-DEVICE-SAME: @_ZN1D6methodEv
|
|
//CHECK-HOST-NOT: @_ZTV1D
|
|
//CHECK-DEVICE-NOT: @_ZTVN10__cxxabiv117__class_type_infoE
|
|
//CHECK-DEVICE-NOT: @_ZTS1D
|
|
//CHECK-DEVICE-NOT: @_ZTI1D
|
|
// This is the case with mixed host and device virtual methods. It's
|
|
// impossible to emit a valid vtable in that case because only host or
|
|
// only device methods would be available during host or device
|
|
// compilation. At the moment Clang (and NVCC) emit NULL pointers for
|
|
// unavailable methods,
|
|
struct HD {
|
|
virtual void h_method();
|
|
__device__ virtual void d_method();
|
|
};
|
|
// CHECK-BOTH: @_ZTV2HD
|
|
// CHECK-DEVICE-NOT: @_ZN2HD8h_methodEv
|
|
// CHECK-DEVICE-SAME: null
|
|
// CHECK-DEVICE-SAME: @_ZN2HD8d_methodEv
|
|
// CHECK-HOST-SAME: @_ZN2HD8h_methodEv
|
|
// CHECK-HOST-NOT: @_ZN2HD8d_methodEv
|
|
// CHECK-HOST-SAME: null
|
|
// CHECK-BOTH-SAME: ]
|
|
// CHECK-DEVICE-NOT: @_ZTVN10__cxxabiv117__class_type_infoE
|
|
// CHECK-DEVICE-NOT: @_ZTS2HD
|
|
// CHECK-DEVICE-NOT: @_ZTI2HD
|
|
|
|
void H::method() {}
|
|
//CHECK-HOST: define{{.*}} void @_ZN1H6methodEv
|
|
|
|
void __device__ D::method() {}
|
|
//CHECK-DEVICE: define{{.*}} void @_ZN1D6methodEv
|
|
|
|
void __device__ HD::d_method() {}
|
|
// CHECK-DEVICE: define{{.*}} void @_ZN2HD8d_methodEv
|
|
// CHECK-HOST-NOT: define{{.*}} void @_ZN2HD8d_methodEv
|
|
void HD::h_method() {}
|
|
// CHECK-HOST: define{{.*}} void @_ZN2HD8h_methodEv
|
|
// CHECK-DEVICE-NOT: define{{.*}} void @_ZN2HD8h_methodEv
|
|
|