stabilize combining +bundle and +whole-archive link modifiers by Be-ing · Pull R...

Could you remove all uses of feature(packed_bundled_libs) from tests?
(This one, for example - tests\run-make\rlib-format-packed-bundled-libs-3\rust_dep.rs.)

The packed_bundled_libs feature should also be stabilized (moved from compiler\rustc_feature\src\active.rs to compiler\rustc_feature\src\accepted.rs).

The packed_bundled_libs feature should also be stabilized (moved from compiler\rustc_feature\src\active.rs to compiler\rustc_feature\src\accepted.rs).

What about the other use of the feature?

The packed_bundled_libs feature should also be stabilized (moved from compiler\rustc_feature\src\active.rs to compiler\rustc_feature\src\accepted.rs).

What about the other use of the feature?

That's a command line option, not feature.

Ah, I didn't realize those were turned on in different ways.

Sorry for letting this sit for a while. @petrochenkov I have rebased it and addressed review comments.

Brief summary

Currently, combining +bundle and +whole-archive works only with #![feature(packed_bundled_libs)]. This crate feature is independent of the -Zpacked-bundled-libs command line option.

This commit stabilizes the #![feature(packed_bundled_libs)] crate feature and implicitly enables it only when the +bundle and +whole-archive link modifiers are combined. This allows rlib crates to use the +whole-archive link modifier with native libraries and have all symbols included in the linked library to be included in downstream staticlib crates that use the rlib as a dependency. Other cases requiring the packed_bundled_libs behavior still require the -Zpacked-bundled-libs command line option, which can be stabilized independently in the future.

Per discussion on #108081 there is no risk of regression stabilizing the crate feature in this way because the combination of +bundle,+whole-archive link modifiers was previously not allowed.

Documentation

I don't think anything needs to be updated for this? From users' perspective it's merely allowing a combination of existing link modifiers that previously failed with an error.

Tests

tests/run-make/rlib-format-packed-bundled-libs-3/rust_dep.rs

Real world example of Rust code requiring this feature: KDAB/cxx-qt#598

Unresolved questions

The -Zpacked-bundled-libs command line option is still unstable.

@rfcbot fcp merge
This PR is a promise that the combination +bundle,+whole-archive in rlibs will be supported in the future in some way (the specific way in which it's supported stays an implementation detail).

Team member @petrochenkov has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

Discussed ion T-compiler meeting on Zulip, acknowledged that it will need sign-off from T-compiler members.

@rustbot label -I-compiler-nominated

🔔 This is now entering its final comment period, as per the review above. 🔔

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

This will be merged soon.

@bors r+

📌 Commit 72e29da has been approved by petrochenkov

It is now in the queue for this repository.

⌛ Testing commit 72e29da with merge 56ada88...

☀️ Test successful - checks-actions
Approved by: petrochenkov
Pushing 56ada88 to master...

Finished benchmarking commit (56ada88): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 631.332s -> 630.734s (-0.09%)
Artifact size: 317.36 MiB -> 317.40 MiB (0.01%)