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

stop disabling frame pointer elimination #8695

Closed
wants to merge 2 commits into from
Closed

stop disabling frame pointer elimination #8695

wants to merge 2 commits into from

Conversation

thestinger
Copy link
Contributor

We currently have no need for the frame pointers on any platform. They
may eventually be needed on platforms without an equivalent to the DWARF
call frame information to walk the stack in the garbage collector.

Closes #7477

using this to turn off the frame pointers isn't needed, and doesn't
actually work right now because the reference to it omits the target
triple
We currently have no need for the frame pointers on any platform. They
may eventually be needed on platforms without an equivalent to the DWARF
call frame information to walk the stack in the garbage collector.

Closes #7477
@thestinger
Copy link
Contributor Author

@graydon: I guess you can revert this commit in the current iteration of the GC, and perhaps there will be a better way of walking the stack (libunwind maybe) by the time it lands.

bors added a commit that referenced this pull request Aug 23, 2013
We currently have no need for the frame pointers on any platform. They
may eventually be needed on platforms without an equivalent to the DWARF
call frame information to walk the stack in the garbage collector.

Closes #7477
@bors bors closed this Aug 23, 2013
brson added a commit to brson/rust that referenced this pull request Aug 29, 2013
…ton"

This reverts commit 2c0f9bd, reversing
changes made to f8c4f0e.

Conflicts:
	src/rustllvm/RustWrapper.cpp
flip1995 pushed a commit to flip1995/rust that referenced this pull request Apr 21, 2022
…ve, r=xFrednet

Fix needless_match false positive for if-let when the else block doesn't match to given expr

<!--

Thank you for making Clippy better!

We're collecting our changelog from pull request descriptions.
If your PR only includes internal changes, you can just write
`changelog: none`. Otherwise, please write a short comment
explaining your change. Also, it's helpful for us that
the lint name is put into brackets `[]` and backticks `` ` ` ``,
e.g. ``[`lint_name`]``.

If your PR fixes an issue, you can add "fixes #issue_number" into this
PR description. This way the issue will be automatically closed when
your PR is merged.

If you added a new lint, here's a checklist for things that will be
checked during review or continuous integration.

- \[ ] Followed [lint naming conventions][lint_naming]
- \[ ] Added passing UI tests (including committed `.stderr` file)
- \[x] `cargo test` passes locally
- \[x] Executed `cargo dev update_lints`
- \[ ] Added lint documentation
- \[x] Run `cargo dev fmt`

[lint_naming]: https://rust-lang.github.io/rfcs/0344-conventions-galore.html#lints

Note that you can skip the above if you are just opening a WIP PR in
order to get feedback.

Delete this line and everything above before opening your PR.

--->

fix rust-lang#8695

*Please write a short comment explaining your change (or "none" for internal only changes)*

changelog: Fixed ``[`needless_match`]`` false positive when else block expression differs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Turn on frame pointer elimination
2 participants