[Backport 7.70.x] Pass canonical target to swiftc on AArch64/ARM64

[agent-platform-auto-pr]

Backport f92d577 from #39641.

---

What does this PR do?

Pass a more canonical¹ target to swiftc for AArch64/ARM64 on macOS:

-swiftc ... -target arm64-apple-macosx11.0 ...
+swiftc ... -target arm64-apple-macos11.0 ...

Motivation

See:

• https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary#Update-the-Architecture-List-of-Custom-Makefiles

  arm_app: main.c
      $(CC) main.c -o arm_app -target arm64-apple-macos11
  

• Offering: changes required for macOS agent builds on Apple Silicon #18173 (comment)

  command 'swiftc -O -swift-version "5" -target "arm64-apple-macos11" -Xlinker \'-rpath\' -Xlinker \'@executable_path/../Frameworks\' Sources/*.swift -o gui', cwd: systray_build_dir
  

• https://stackoverflow.com/a/73773711
  > Is there a generic -target I can use that will work for all macOS versions (maybe even future versions)?
  >
  > Yes. For example, if you are targeting macos 11, you can use -target x86_64-apple-macos11.0 for intel CPUs and arm64-apple-macos11.0 for apple silicon CPUs. By default, targeting macos 11 means you can run the binary in future macos version.

Describe how you validated your changes

Successful build.

Additional Notes

Footnotes

1. preferred, if not recommended ↩

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a038ce2d-7b70-4a7d-955a-c16ba443ff92

Baseline: 8f302fd
Comparison: ea3e8ad
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	-1.68	[-4.78, +1.42]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	tcp_syslog_to_blackhole	ingress throughput	+0.62	[+0.57, +0.68]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.51	[+0.47, +0.55]	1	Logs
➖	docker_containers_memory	memory utilization	+0.45	[+0.41, +0.49]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.22	[-2.55, +2.98]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	+0.21	[+0.09, +0.34]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.15	[+0.00, +0.29]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	+0.11	[-0.28, +0.50]	1	Logs bounds checks dashboard
➖	ddot_metrics	memory utilization	+0.04	[-0.07, +0.16]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.33, +0.34]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.02, +0.02]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.00	[-0.60, +0.60]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.01	[-0.60, +0.57]	1	Logs
➖	file_tree	memory utilization	-0.02	[-0.05, +0.02]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.04	[-0.63, +0.55]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.05	[-0.70, +0.61]	1	Logs
➖	quality_gate_idle	memory utilization	-0.08	[-0.12, -0.05]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.19	[-0.22, -0.16]	1	Logs bounds checks dashboard
➖	ddot_logs	memory utilization	-0.27	[-0.36, -0.18]	1	Logs
➖	docker_containers_cpu	% cpu utilization	-1.68	[-4.78, +1.42]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.