Skip to content

error on invalid macho section specifier#155065

Open
folkertdev wants to merge 4 commits intorust-lang:mainfrom
folkertdev:macho-section-specifier
Open

error on invalid macho section specifier#155065
folkertdev wants to merge 4 commits intorust-lang:mainfrom
folkertdev:macho-section-specifier

Conversation

@folkertdev
Copy link
Copy Markdown
Contributor

@folkertdev folkertdev commented Apr 9, 2026

View all comments

The macho section specifier used by #[link_section = "..."] is more strict than e.g. the one for elf. LLVM will error when you get it wrong, which is easy to do if you're used to elf. So, provide some guidance for the simplest mistakes, based on the LLVM validation.

Currently compilation fails with an LLVM error, see https://godbolt.org/z/WoE8EdK1K.

The LLVM validation logic is at

https://github.com/llvm/llvm-project/blob/a0f0d6342e0cd75b7f41e0e6aae0944393b68a62/llvm/lib/MC/MCSectionMachO.cpp#L199-L203

LLVM validates the other components of the section specifier too, but it feels a bit fragile to duplicate those checks. If you get that far, hopefully the LLVM errors will be sufficient to get unstuck.


sidequest from #147811

r? JonathanBrouwer

specifically, is this the right place for this sort of validation? rustc_attr_parsing also does some validation.

@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 9, 2026

Some changes occurred in compiler/rustc_hir/src/attrs

cc @jdonszelmann, @JonathanBrouwer

Some changes occurred in compiler/rustc_passes/src/check_attr.rs

cc @jdonszelmann, @JonathanBrouwer

Some changes occurred in compiler/rustc_attr_parsing

cc @jdonszelmann, @JonathanBrouwer

@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Apr 9, 2026
@folkertdev
Copy link
Copy Markdown
Contributor Author

just in case we're doing something weird that never got built or linked

@bors try jobs=aarch64-apple

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Apr 9, 2026
error on invalid macho section specifier


try-job: aarch64-apple
@rust-log-analyzer

This comment has been minimized.

@folkertdev folkertdev force-pushed the macho-section-specifier branch from 35e0a3f to c90d31f Compare April 9, 2026 20:21
@rustbot rustbot added the A-rustdoc-json Area: Rustdoc JSON backend label Apr 9, 2026
@JonathanBrouwer
Copy link
Copy Markdown
Contributor

specifically, is this the right place for this sort of validation? rustc_attr_parsing also does some validation.

We're trying to move as many checks as possible to attribute parsing, with the "parse, don't validate" mentality, so if an attribute gets through parsing you can assume it is correct. Therefore I'd like this to be in the attribute parser

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 9, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 9, 2026

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@rust-log-analyzer

This comment has been minimized.

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 9, 2026

💔 Test for 3e6930f failed: CI. Failed job:

@rust-log-analyzer

This comment has been minimized.

@folkertdev folkertdev force-pushed the macho-section-specifier branch from c90d31f to 30b9c6e Compare April 9, 2026 22:49
@rust-bors

This comment has been minimized.

@JonathanBrouwer JonathanBrouwer force-pushed the macho-section-specifier branch from 30b9c6e to db42ae2 Compare April 10, 2026 09:31
@JonathanBrouwer

This comment was marked as outdated.

@rustbot

This comment has been minimized.

@rust-bors

This comment was marked as outdated.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Apr 10, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Apr 10, 2026
…, r=JonathanBrouwer

error on invalid macho section specifier

The macho section specifier used by `#[link_section = "..."]` is more strict than e.g. the one for elf. LLVM will error when you get it wrong, which is easy to do if you're used to elf. So, provide some guidance for the simplest mistakes, based on the LLVM validation.

Currently compilation fails with an LLVM error, see https://godbolt.org/z/WoE8EdK1K.

The LLVM validation logic is at

https://github.com/llvm/llvm-project/blob/a0f0d6342e0cd75b7f41e0e6aae0944393b68a62/llvm/lib/MC/MCSectionMachO.cpp#L199-L203

LLVM validates the other components of the section specifier too, but it feels a bit fragile to duplicate those checks. If you get that far, hopefully the LLVM errors will be sufficient to get unstuck.

---

sidequest from rust-lang#147811

r? JonathanBrouwer

specifically, is this the right place for this sort of validation? `rustc_attr_parsing` also does some validation.
@folkertdev folkertdev force-pushed the macho-section-specifier branch from a5691b8 to 896d75e Compare April 12, 2026 12:47
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 12, 2026

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@folkertdev
Copy link
Copy Markdown
Contributor Author

@bors try jobs=aarch64-apple

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Apr 12, 2026
error on invalid macho section specifier


try-job: aarch64-apple
pub(crate) struct LinkSectionParser;

fn check_link_section_macho(name: Symbol) -> Result<(), InvalidMachoSectionReason> {
let mut parts = name.as_str().split(',').map(|s| s.trim());
Copy link
Copy Markdown
Member

@bjorn3 bjorn3 Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

View changes since the review

Does LLVM also trim? I don't trim in cg_clif when parsing section names.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 12, 2026

💔 Test for 5c7f2d3 failed: CI. Failed job:

@rust-log-analyzer

This comment has been minimized.

@madsmtm madsmtm added the O-apple Operating system: Apple / Darwin (macOS, iOS, tvOS, visionOS, watchOS) label Apr 12, 2026
@folkertdev folkertdev force-pushed the macho-section-specifier branch from 896d75e to 3f4778b Compare April 12, 2026 16:16
@rustbot rustbot added the T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. label Apr 12, 2026
@folkertdev
Copy link
Copy Markdown
Contributor Author

@bors try jobs=aarch64-apple

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Apr 12, 2026
error on invalid macho section specifier


try-job: aarch64-apple
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 12, 2026

💔 Test for b88cc98 failed: CI. Failed job:

@rust-log-analyzer

This comment has been minimized.

@folkertdev folkertdev force-pushed the macho-section-specifier branch from 3f4778b to 7aeba4e Compare April 12, 2026 19:07
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 12, 2026

These commits modify tests/rustdoc-json.
rustdoc-json is a public (but unstable) interface.

Please ensure that if you've changed the output:

  • It's intentional.
  • The FORMAT_VERSION in src/librustdoc-json-types is bumped if necessary.

cc @aDotInTheVoid, @obi1kenobi

@folkertdev
Copy link
Copy Markdown
Contributor Author

@bors try jobs=aarch64-apple

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Apr 12, 2026
error on invalid macho section specifier


try-job: aarch64-apple
@folkertdev
Copy link
Copy Markdown
Contributor Author

btw there is some discussion at #t-lang > error on invalid macho section about whether we should FCW this first.

This change might break projects that use an invalid section specifier for a symbol that never gets linked. Currently LLVM's codegen would never see that symbol, but with this change rustc will error early.

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 12, 2026

☀️ Try build successful (CI)
Build commit: 6c29d2f (6c29d2f2952cde2f07cef44fa298d1b9180dd914, parent: dab8d9d1066c4c95008163c7babf275106ce3f32)

Copy link
Copy Markdown
Contributor

@JonathanBrouwer JonathanBrouwer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r=me if T-lang is happy

View changes since this review

@folkertdev folkertdev added the I-lang-nominated Nominated for discussion during a lang team meeting. label Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-rustdoc-json Area: Rustdoc JSON backend A-test-infra-minicore Area: `minicore` test auxiliary and `//@ add-core-stubs` I-lang-nominated Nominated for discussion during a lang team meeting. O-apple Operating system: Apple / Darwin (macOS, iOS, tvOS, visionOS, watchOS) S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants