-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Don't infer attributes of virtual calls based on the function body #137669
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
Changes from all commits
Commits
Show all changes
3 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
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
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,37 @@ | ||
//! Regression test for https://github.com/rust-lang/rust/issues/137646. | ||
//! Since we don't know the exact implementation of the virtual call, | ||
//! it might write to parameters, we can't infer the readonly attribute. | ||
//@ compile-flags: -C opt-level=3 -C no-prepopulate-passes | ||
|
||
#![crate_type = "lib"] | ||
#![feature(rustc_attrs)] | ||
|
||
pub trait Trait { | ||
#[rustc_nounwind] | ||
fn m(&self, _: (i32, i32, i32)) {} | ||
} | ||
|
||
#[no_mangle] | ||
pub fn foo(trait_: &dyn Trait) { | ||
// CHECK-LABEL: @foo( | ||
// CHECK: call void | ||
// CHECK-NOT: readonly | ||
trait_.m((1, 1, 1)); | ||
} | ||
|
||
#[no_mangle] | ||
#[rustc_nounwind] | ||
pub fn foo_nounwind(trait_: &dyn Trait) { | ||
// CHECK-LABEL: @foo_nounwind( | ||
// FIXME: Here should be invoke. | ||
// COM: CHECK: invoke | ||
trait_.m((1, 1, 1)); | ||
} | ||
|
||
#[no_mangle] | ||
pub extern "C" fn c_nounwind(trait_: &dyn Trait) { | ||
// CHECK-LABEL: @c_nounwind( | ||
// FIXME: Here should be invoke. | ||
// COM: CHECK: invoke | ||
trait_.m((1, 1, 1)); | ||
} |
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,45 @@ | ||
//! Regression test for https://github.com/rust-lang/rust/issues/137646. | ||
//! The parameter value at all calls to `check` should be `(1, 1, 1)`. | ||
|
||
//@ run-pass | ||
|
||
use std::hint::black_box; | ||
|
||
type T = (i32, i32, i32); | ||
|
||
pub trait Trait { | ||
fn m(&self, _: T, _: T) {} | ||
} | ||
|
||
impl Trait for () { | ||
fn m(&self, mut _v1: T, v2: T) { | ||
_v1 = (0, 0, 0); | ||
check(v2); | ||
} | ||
} | ||
|
||
pub fn run_1(trait_: &dyn Trait) { | ||
let v1 = (1, 1, 1); | ||
let v2 = (1, 1, 1); | ||
trait_.m(v1, v2); | ||
} | ||
|
||
pub fn run_2(trait_: &dyn Trait) { | ||
let v1 = (1, 1, 1); | ||
let v2 = (1, 1, 1); | ||
trait_.m(v1, v2); | ||
check(v1); | ||
check(v2); | ||
} | ||
|
||
#[inline(never)] | ||
fn check(v: T) { | ||
assert_eq!(v, (1, 1, 1)); | ||
} | ||
|
||
fn main() { | ||
black_box(run_1 as fn(&dyn Trait)); | ||
black_box(run_2 as fn(&dyn Trait)); | ||
run_1(&()); | ||
run_2(&()); | ||
} |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you apply
#[rustc_nounwind]
on a trait method, it should be fine to assume that all calls of this trait method don't unwind, right? If any of the implementations doesn't use#[rustc_nounwind]
, that should probably be reported as error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it stands, the semantics are somewhat ambiguous; rustc currently only applies this to the annotated function. But I also think the constraint is fine. I will create an issue for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#137765