-
Notifications
You must be signed in to change notification settings - Fork 303
Add post for Rust 1.80.1 #1373
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
Merged
Merged
Add post for Rust 1.80.1 #1373
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
layout: post | ||
title: "Announcing Rust 1.80.1" | ||
author: The Rust Release Team | ||
release: true | ||
--- | ||
|
||
The Rust team has published a new point release of Rust, 1.80.1. Rust is a | ||
programming language that is empowering everyone to build reliable and | ||
efficient software. | ||
|
||
If you have a previous version of Rust installed via rustup, getting Rust | ||
1.80.1 is as easy as: | ||
|
||
``` | ||
rustup update stable | ||
``` | ||
|
||
If you don't have it already, you can [get `rustup`][rustup] from the | ||
appropriate page on our website. | ||
|
||
[rustup]: https://www.rust-lang.org/install.html | ||
|
||
## What's in 1.80.1 | ||
|
||
Rust 1.80.1 fixes two regressions that were recently reported. | ||
|
||
### Miscompilation when comparing floats | ||
|
||
In addition to the existing optimizations performed by LLVM, rustc is growing | ||
its own set of optimizations. Rust 1.78.0 added a new one, implementing ["jump | ||
threading"] (merging together two adjacent branches performing the same | ||
comparison). | ||
|
||
The optimization was also enabled on branches checking for floating point | ||
equality, but it didn't implement the special rules needed for floats | ||
comparison (`NaN != NaN` and `0.0 == -0.0`). This caused the optimization to | ||
miscompile code performing those checks. | ||
|
||
Rust 1.80.1 addresses the problem by preventing the optimization from being | ||
applied to float comparisons, while retaining the optimization on other | ||
supported types. | ||
|
||
### False positives in the `dead_code` lint | ||
|
||
Rust 1.80.0 contained refactorings to the `dead_code` lint. We received | ||
multiple reports that the new lint implementation produces false positives, so | ||
we are reverting the changes in Rust 1.80.1. We'll continue to experiment on | ||
how to improve the accuracy of `dead_code` in future releases. | ||
|
||
## Contributors to 1.80.1 | ||
|
||
Many people came together to create Rust 1.80.1. We couldn't have done it | ||
without all of you. [Thanks!](https://thanks.rust-lang.org/rust/1.80.1/) | ||
|
||
["jump threading"]: https://en.wikipedia.org/wiki/Jump_threading |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.