--print=native-static-libs produces no output for `#![no_std]` staticlib

[pnkfelix]

(spawned off of #53281 (comment) )
I tried this code:

// compile-args: -Cpanic=abort --print=native-static-libs /tmp/hello.rs
#![crate_type="staticlib"]

#![no_std]

use core::panic::PanicInfo;
#[panic_handler]
fn panic(_info: &PanicInfo) -> ! {
    loop { }
}

I expected to see this happen:

A line of output that includes the prefix:

note: Link against the following native artifacts when linking against this static library. The order and any duplication can be significant on some platforms.

note: native-static-libs: [...]

Instead, this happened:

No output.

Meta

rustc --version --verbose:

rustc 1.70.0-nightly (7820b62d2 2023-03-05)
binary: rustc
commit-hash: 7820b62d20bc548096d4632a3487987308cb4b5d
commit-date: 2023-03-05
host: x86_64-unknown-linux-gnu
release: 1.70.0-nightly
LLVM version: 15.0.7

[pnkfelix]

• I'm trying to figure out whether the lack of output in that scenario is by design.
• One mindset about a staticlib crate is that it is a standalone deliverable, with no symbols that remain to be linked in.
• However, I do not think our current staticlib output satisfies that criteria, and thus I suspect it still makes sense for a staticlib crate to support --print=native-static-libs.

[pnkfelix]

Oh, I think this will actually get fixed by PR #106560

[bjorn3]

Yeah, I removed the if !all_native_libs.is_empty() condition in #106560.

[bjorn3]

Looks like there is still the if !lib_args.is_empty() condition.