You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Boxes provide the simplest form of heap allocation in Rust. However, because they own a pointer, flowistry conservatively considers a maximum (unknown) region for them causing all of them to be grouped under a single alias group.
This behavior seems to be an exception, which can be rooted here.
As Boxes are probably the most-used structure for heap allocation, improving the precision of the analysis for them and avoiding reasoning about the pointer inside them can help a lot. It also affects the results for other types such as vectors when they use boxes. (e.g., using into_boxed_slice or some forms of vec! macro).
The text was updated successfully, but these errors were encountered:
Box
es provide the simplest form of heap allocation in Rust. However, because they own a pointer, flowistry conservatively considers a maximum (unknown) region for them causing all of them to be grouped under a single alias group.This behavior seems to be an exception, which can be rooted here.
flowistry/crates/flowistry/src/mir/utils.rs
Lines 613 to 614 in a156ab9
As
Box
es are probably the most-used structure for heap allocation, improving the precision of the analysis for them and avoiding reasoning about the pointer inside them can help a lot. It also affects the results for other types such as vectors when they use boxes. (e.g., usinginto_boxed_slice
or some forms ofvec!
macro).The text was updated successfully, but these errors were encountered: