Skip to content

rt: don't save and restore xmm/regs in __morestack. #5418

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

Closed
wants to merge 1 commit into from

Conversation

luqmana
Copy link
Member

@luqmana luqmana commented Mar 17, 2013

Like I commented in #2043, I can't reproduce the weirdness from #1388 on either mac or linux (x84_64) and pushing to try gives all green.

That's 128 less bytes to have to keep in the stack for every call to __morestack.

@graydon
Copy link
Contributor

graydon commented Mar 18, 2013

Hm. I'm still not sure why they were being clobbered in the meantime. Maybe there was an SSE-using memmove somewhere unaccounted for, or we failed to preserve them across task switches or something?

@brson
Copy link
Contributor

brson commented Mar 25, 2013

I'm wary of landing this before 0.6 since I don't think anything notable has changed on the __morestack path to make this problem go away and hitting it depends on exactly where the end of the stack segment is and possibly whether there is already a cached segment.

@brson
Copy link
Contributor

brson commented Apr 18, 2013

OK, let's merge this and see what happens!

bors added a commit that referenced this pull request Apr 18, 2013
Like I commented in #2043, I can't reproduce the weirdness from #1388 on either mac or linux (x84_64) and pushing to try gives all green.

That's 128 less bytes to have to keep in the stack for every call to __morestack.
@bors bors closed this Apr 18, 2013
oli-obk pushed a commit to oli-obk/rust that referenced this pull request May 2, 2020
Downgrade unreadable_literal to pedantic

As motivated by rust-lang#5418. This is the top most commonly suppressed Clippy style lint, which indicates that the community has decided they don't share Clippy's opinion on the best style of this.

I've left the lint in as pedantic, though it could be that "restriction" would be better -- I can see this lint being useful as an opt-in restriction in some codebases.

changelog: Remove unreadable_literal from default set of enabled lints
oli-obk pushed a commit to oli-obk/rust that referenced this pull request May 2, 2020
Downgrade new_ret_no_self to pedantic

As motivated by rust-lang#5418. This is the second most widely suppressed Clippy style lint, and [this grep.app search](https://grep.app/search?q=%5C%5Ballow%5C%28.%2Aclippy%3A%3Anew_ret_no_self%5Cb&regexp=true&case=true&filter[lang][0]=Rust) shows a large number of diverse reasonable signatures for a `new` method.

changelog: Remove new_ret_no_self from default set of enabled lints
oli-obk pushed a commit to oli-obk/rust that referenced this pull request May 2, 2020
compare with the second largest instead of the smallest variant

This should make the lint less noisy for now. See [my comment](rust-lang/rust-clippy#5418 (comment)) to issue rust-lang#5418.

---

changelog: none
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.

4 participants