Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Functions may not appear in output when using rust >= v1.75.0 #5939

Closed
sadlerap opened this issue Jan 3, 2024 · 2 comments · Fixed by #6013
Closed

[BUG]: Functions may not appear in output when using rust >= v1.75.0 #5939

sadlerap opened this issue Jan 3, 2024 · 2 comments · Fixed by #6013

Comments

@sadlerap
Copy link

sadlerap commented Jan 3, 2024

Describe the bug

Assembly output filtering appears to be overfiltering some functions from Rust's compiler output for rust versions >= v1.75.0. Appears to also happen with nightly versions.

Steps to reproduce

  1. Visit godbolt.org
  2. Change language in source pane to Rust (the default source listing is enough)
  3. Enable optimization flags (-O is enough to reproduce)
  4. View output pane

Expected behavior

The assembly output of the default function should be there.

Reproduction link

https://godbolt.org/z/s8nnqv377

Screenshots

Not applicable

Operating System

No response

Browser version

No response

@sadlerap sadlerap added the bug label Jan 3, 2024
@partouf
Copy link
Contributor

partouf commented Jan 4, 2024

The issue and possible solutions are discussed here #5782
This is really just due to how the compiler behaves.

But as far as CE is concerned, we have no plans changing the behavior unless someone sends a PR that can address this, for example a new default sourcecode so people know how to circumvent the issue.

For example adding #[inline(never)] with a description of it

@partouf partouf added lang-rust and removed bug labels Jan 4, 2024
@RalfJung
Copy link

rust-lang/rust#119850 tracks this issue on the Rust side.

jeremy-rifkin pushed a commit that referenced this issue Jan 17, 2024
…output (#6013)

Resolves #5939.

Rust issue about this problem:
rust-lang/rust#119850

Hopefully this can be reverted again when there is a fix on the Rust
side.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants