-
Notifications
You must be signed in to change notification settings - Fork 353
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
Implement missing shims for Windows #1537
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Miri is great project, thanks! I am trying to use miri on a regression test on windows, which uses
To my understanding from this issue is that file system access is still not implemented for windows (it was added for Unix platforms 2019 in #923. Is there a workaround for reading a regression reference in windows, such that miri does not complain (unfortunately I cannot use |
@mbyt you can run Miri with |
Since most of the small things are done now, I'll close this issue in favor of one that is specifically about file system access: #3482. |
Here we track shims that Miri currently only implements for Linux and macOS targets, but not for Windows.
If you run into this, try
cargo miri test --target x86_64-unknown-linux-gnu
. This works even on a Windows host (without installing anything extra) and interprets programs on a well-supported Linux target.std::thread::sleep
std::sync
The text was updated successfully, but these errors were encountered: