Comments (12)
I just learned from this blog post that the Linux kernel repo has four initial commits. It doesn't seem like a big deal. One of their roots was even added by accident.
from miri.
There is an integration plan from last week's compiler design sprint here.
from miri.
interp
interpret
, surely.
from miri.
An open question is how to integrate miri's source into rustc:
- go the
rls
way: integrate the miri repository as a submodule of the rustc repository - go the
clippy
way: move the miri library into the rustc repository and only develop the miri executable in this repository.
@solson: have you done any work towards moving miri into rustc, or are planning on doing so any time soon? If not, do you mind if I give it a try?
from miri.
I haven't done any merging work yet, but I plan to do it relatively soon.
My basic idea was to create a mir_interp
or mir::interp
module somewhere (wherever @eddyb suggests) and get the code compiling there. I don't think we should use a submodule, so I agree with only developing the executable in this repo. It could depend on the rustc code, but that would limit experimentation in this repo (e.g. doing FFI calls) so maybe it should just exist separately. Unfortunately that requires manual syncing of the code...
We'll have to get rid of our dependency on the byteorder crate before merging into rustc.
from miri.
that would limit experimentation in this repo
I have an abstraction layer in mind, so the bulk of the code stays in the compiler and here you keep a driver and extensions to it.
from miri.
We'll have to get rid of our dependency on the byteorder crate before merging into rustc.
If you wait a few more days, the old makefiles are getting removed and you can just depend on crates.io.
from miri.
If I may recommend, git subtree
is nice for preserving history with this sort of thing.
from miri.
git subtree
showed up on IRC before, I believe my suggestion was to have a merge commit between two repos (connected by a git remote
).
Now there's a way to actually make the commits valid in this repo: make a commit to move the files in the right position and roughly the right content, on a miri branch, then merge that branch into Rust.
from miri.
@brson @alexcrichton Would there be serious issues if we ended up with two roots (commits with no parents) in rust-lang/rust, in order to preserve miri's history? We can do something else otherwise.
from miri.
I don't really understand what the implications of such a situation would be, but I can't think of any reason offhand why that'd be bad
from miri.
Closing this, since Miri was in fact merged into rustc back in December in rust-lang/rust#45002, and later fully replaced the old const evaluator in rust-lang/rust#46882 just a couple weeks ago. (Thanks @oli-obk and everyone else involved!)
from miri.
Related Issues (20)
- Running `Cargo miri test` on `cargo`, an error occurred HOT 6
- Massive slowdown caused by stacked borrows on code involving raw pointers + UnsafeCell HOT 6
- Programs that cast function pointers have escalating memory use HOT 1
- Support `SystemTime` with enabled isolation HOT 4
- Implement pipe/pipe2 HOT 1
- pthreads synchronization primitives: detect mutex/rwlock/... being moved to a different location HOT 8
- FFI implementation libc getuid on Linux HOT 2
- False positive deadlock with `pollster` and async HOT 2
- Support miri-specific entry point / start function for no-std binaries
- Miri can't call foreign function `mi_malloc_aligned` on OS `linux` HOT 1
- Tree-borrows false positive with `iter::Extend`? HOT 5
- offset_from "same allocation" check is confused by int-to-ptr casts HOT 3
- Are unclosed file descriptors a memory leak? HOT 3
- Project idea: strongly typed file descriptor integers and deduplication of various checks around them HOT 4
- false positive with SB+TB: "Shifting" of a value HOT 6
- `cargo miri test` fails without `RUSTC` env var HOT 3
- Undefined behavior from `poll_fn` + `futures::join!` / `std::future::join!` HOT 11
- Tail calls end protectors too early HOT 2
- !Send Future violates stacked borrow rules HOT 10
- Implicit reborrows do not cause writes HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from miri.