Files
RedBear-OS/local/recipes/dev/libclc/source/clang/test/CodeGenObjC/instance-method-metadata.m
T
vasilito cb424d7448 build: static patch-sanity linter (shift-left the malformed-patch class)
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).
2026-08-01 05:13:02 +03:00

33 lines
824 B
Objective-C

// REQUIRES: x86-registered-target
// RUN: %clang_cc1 -triple x86_64-apple-darwin10 -S %s -o - | FileCheck %s
/** The problem looks like clang getting confused when a single translation unit
contains a protocol with a property and two classes that implement that protocol
and synthesize the property.
*/
@protocol Proto
@property (assign) id prop;
@end
@interface NSObject @end
@interface Foo : NSObject <Proto> { int x; } @end
@interface Bar : NSObject <Proto> @end
@implementation Foo
@synthesize prop;
@end
@implementation Bar
@synthesize prop;
@end
// CHECK: _OBJC_$_INSTANCE_METHODS_Bar:
// CHECK-NEXT: .long 24
// CHECK-NEXT: .long 2
// CHECK-NEXT: .quad L_OBJC_METH_VAR_NAME_
// CHECK-NEXT: .quad L_OBJC_METH_VAR_TYPE_
// CHECK-NEXT: .quad "-[Bar prop]"