[NativeAOT] Migrate shared GC logging to printf

[jonathanpeppers]

Summary

Continue the printf-style native logging migration by converting the remaining formatted diagnostics in the shared GC bridge and logger setup paths compiled into the NativeAOT host.

This PR follows the runtime utility migration merged in #12148 and reuses the canonical shared printf declarations established by #12155. It now targets main after its stacked dependencies merged.

Part of #12139.

Scope

• migrate temporary-peer capacity and GC cleanup summary diagnostics in bridge-processing.cc;
• migrate debug-only missing Java method diagnostics while preserving null-safe class-name output;
• migrate reference-log file open and invalid-path diagnostics in logger.cc;
• return static string-segment error messages as C strings for direct %s logging;
• remove six std::format-style logging instantiations from NativeAOT-reachable shared sources.

Behavior preservation

• logging categories and existing debug/category gates are unchanged;
• size_t values use %zu;
• raw nullable class names continue through optional_string();
• non-owning path and file-kind views use bounded %.*s output;
• static string-segment error messages use %s without an intermediate std::string_view;
• message text, punctuation, source locations, and control flow are unchanged;
• warning and error diagnostics remain unconditional, while debug and info diagnostics retain helper-level category gating.

Non-goals

• This PR does not change the logging implementation or declarations.
• It does not migrate the nearby gref std::format strings passed to OSBridge::_monodroid_gref_log; those feed a separate file/log pipeline and require a dedicated API design.
• It does not touch formatting outside NativeAOT-reachable shared sources.

Validation

• dotnet-local.cmd build src\native\native-nativeaot.csproj -p:AndroidSupportedTargetJitAbis=arm64-v8a
• dotnet-local.cmd build src\native\native-clr.csproj -p:AndroidSupportedTargetJitAbis=arm64-v8a
• git diff --check
• focused review of printf types, category gating, null handling, bounded string views, and control flow

[Copilot]

Pull request overview

This PR continues the NativeAOT printf-style logging migration by converting remaining std::format-style formatted diagnostics in NativeAOT-reachable shared sources (GC bridge paths and reference-log setup) to the log_*f() printf helpers, while preserving existing category gating and null-safe string handling.

Changes:

• Converted GC bridge diagnostics in bridge-processing.cc to log_*f() with %zu for size_t and %s via optional_string() for nullable class names.
• Converted reference-log file open and invalid-path diagnostics in logger.cc to log_*f() using bounded %.*s formatting for std::string_view.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/native/clr/runtime-base/logger.cc	Migrates reference-log file path diagnostics from {} formatting to bounded printf-style logging.
src/native/clr/host/bridge-processing.cc	Migrates GC bridge temporary-peer/local-capacity and GC cleanup summary diagnostics to printf-style logging.

[jonathanpeppers]

/review

[github-actions]

✅ Android PR Reviewer completed successfully!

[github-actions]

✅ LGTM

Clean, well-scoped continuation of the printf-style native logging migration. I verified the changes independently against the full source before reading the description.

Verification highlights:

• bridge-processing.cc — map_capacity, total, and alive are all size_t (lines 15, 580–581), so %zu is the correct specifier. optional_string(class_name) returns const char*, matching %s. Debug-only gating (#if ...) around the missing-method diagnostics is preserved.
• logger.cc — path and file_kind are std::string_view; the %.*s + static_cast<int>(len) + .data() pattern is the correct way to print a non-null-terminated view. to_string(file_name.error()) now yields const char*, matching %s.
• strings.hh — to_string(string_segment_error) return-type change from std::string_view to const char* has exactly one caller (logger.cc:201), which is updated correctly. No other consumers depend on the old string_view return.
• All log_*f overloads used exist in shared/log_functions.hh with __attribute__((format(printf,...))), so the compiler validates the format strings — mismatches would fail the build.
• Message text, categories, punctuation, and control flow are unchanged, as claimed.

CI: dotnet-android completed neutral (not a failure); license/cla passed. No PR-caused failures.

Counts: 0 ❌ · 0 ⚠️ · 1 💡 (optional constexpr on to_string). Nice, mechanically-faithful migration.

Generated by Android PR Reviewer for #12210 · 65.9 AIC · ⌖ 12.8 AIC · ⊞ 6.8K
_{Comment /review to run again}

[jonathanpeppers]

The one test failure was addressed in another PR: