mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
9a6450af95
rust/Cargo.lock

624 lines
15 KiB
Plaintext
Raw Normal View History

add lockfile
2019-10-14 02:38:08 -05:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
'cargo update' all the things
2021-04-04 04:11:19 -05:00
version = 3
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "aho-corasick"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.7.18"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "1e37cfd5e7657ada45f742d6e99ca5788580b5c529dc78faf11ece6dc702656f"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"memchr",
add lockfile
2019-10-14 02:38:08 -05:00
]
bump dependencies
2020-03-08 10:29:57 -05:00
[[package]]
name = "anyhow"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.51"
bump dependencies
2020-03-08 10:29:57 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "8b26702f315f53b6071259e15dd9d64528213b44d61de1ec926eca7715d62203"
bump dependencies
2020-03-08 10:29:57 -05:00
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "atty"
cargo update
2020-02-23 15:44:16 -06:00
version = "0.2.14"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"hermit-abi",
"libc",
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
'cargo update' all the things
2021-04-04 04:11:19 -05:00
[[package]]
name = "bitflags"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.3.2"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
rustup + cargo update
2020-12-17 05:53:10 -06:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "colored"
update for major version bumps
2020-09-18 05:17:09 -05:00
version = "2.0.0"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update for major version bumps
2020-09-18 05:17:09 -05:00
checksum = "b3616f750b84d8f0de8a58bda93e08e2a81ad3f523089b05f1dffecab48c6cbd"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"atty",
"lazy_static",
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "compiletest_rs"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.7.1"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "29843cb8d351febf86557681d049d1e1652b81a086a190fa1173c07fd17fbf83"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"diff",
"filetime",
"getopts",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"lazy_static",
Update lockfile
2020-08-20 18:48:35 -05:00
"libc",
"log",
"miow",
"regex",
"rustfix",
"serde",
"serde_derive",
"serde_json",
"tempfile",
"tester",
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "diff"
cargo update
2020-02-23 15:44:16 -06:00
version = "0.1.12"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "0e25ea47919b1560c4e3b7fe0aaab9becf5b84a10325ddf7db0f0ba5e1026499"
add lockfile
2019-10-14 02:38:08 -05:00
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
[[package]]
bump miri dependencies
2021-04-04 04:45:09 -05:00
name = "dirs-next"
version = "2.0.0"
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump miri dependencies
2021-04-04 04:45:09 -05:00
checksum = "b98cf8ebf19c3d1b223e151f99a4f9f0690dca41414773390fc824184ac833e1"
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"cfg-if",
"dirs-sys-next",
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
bump miri dependencies
2021-04-04 04:45:09 -05:00
name = "dirs-sys-next"
version = "0.1.2"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump miri dependencies
2021-04-04 04:45:09 -05:00
checksum = "4ebda144c4fe02d1f7ea1a7d9641b6fc6b580adcfa024ae48797ecdeb6825b4d"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"libc",
"redox_users",
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "env_logger"
Update dependencies
2021-10-01 16:08:58 -05:00
version = "0.9.0"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies
2021-10-01 16:08:58 -05:00
checksum = "0b2cf0344971ee6c64c31be0d530793fba457d322dfec2810c453d0ef228f9c3"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"atty",
"humantime",
"log",
"regex",
"termcolor",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "filetime"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.15"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "975ccf83d8d9d0d84682850a38c8169027be83368805971cc4f238c2b245bc98"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"cfg-if",
Update lockfile
2020-08-20 18:48:35 -05:00
"libc",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"redox_syscall",
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "getopts"
version = "0.2.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "14dbbfd5c71d70241ecf9e6f13737f7b5ce823821063188d7e46c41d371eebd5"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"unicode-width",
add lockfile
2019-10-14 02:38:08 -05:00
]
update for major version bumps
2020-09-18 05:17:09 -05:00
[[package]]
name = "getrandom"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.3"
update for major version bumps
2020-09-18 05:17:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "7fcd999463524c52659517fe2cea98493cfe485d10565e7b0fb07dbba7ad2753"
update for major version bumps
2020-09-18 05:17:09 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"cfg-if",
update for major version bumps
2020-09-18 05:17:09 -05:00
"libc",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"wasi",
update for major version bumps
2020-09-18 05:17:09 -05:00
]
cargo update
2020-02-23 15:44:16 -06:00
[[package]]
name = "hermit-abi"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.1.19"
cargo update
2020-02-23 15:44:16 -06:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
cargo update
2020-02-23 15:44:16 -06:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"libc",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "humantime"
bump miri dependencies
2021-04-04 04:45:09 -05:00
version = "2.1.0"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump miri dependencies
2021-04-04 04:45:09 -05:00
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
add lockfile
2019-10-14 02:38:08 -05:00
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "instant"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.1.12"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
dependencies = [
"cfg-if",
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "itoa"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.1"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "1aab8fc367588b89dcee83ab0fd66b72b50b72fa1904d7095045ace2b0c81c35"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "libc"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.112"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "1b03d17f364a3a042d5e5d46b053bbbf82c92c9430c592dd4c064dc6ee997125"
add lockfile
2019-10-14 02:38:08 -05:00
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "lock_api"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.4.5"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "712a4d093c9976e24e7dbca41db895dabcbac38eb5f4045393d17a95bdfb1109"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
dependencies = [
"scopeguard",
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "log"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
version = "0.4.14"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
checksum = "51b9bbe6c47d51fc3e1a9b945965946b4c44142ab8792c50835a980d362c2710"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"cfg-if",
add lockfile
2019-10-14 02:38:08 -05:00
]
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "measureme"
Address review comments
2021-05-29 17:09:46 -05:00
version = "9.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "78f7a41bc6f856a2cf0e95094ad5121f82500e2d9a0f3c0171d98f6566d8117d"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
dependencies = [
"log",
"memmap2",
"parking_lot",
"perf-event-open-sys",
"rustc-hash",
"smallvec",
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "memchr"
update lockfile
2021-12-14 11:20:03 -06:00
version = "2.4.1"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "308cc39be01b73d0d18f82a0e7b2a3df85245f84af96fdddc5d202d27e47b86a"
add lockfile
2019-10-14 02:38:08 -05:00
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "memmap2"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.3"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "723e3ebdcdc5c023db1df315364573789f8857c11b631a2fdfad7c00f5c046b4"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
dependencies = [
"libc",
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "miow"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
version = "0.3.7"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
checksum = "b9f1c5b025cda876f66ef43a113f91ebc9f4ccef34843000e0adf6ebbab84e21"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "miri"
version = "0.1.0"
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"colored",
"compiletest_rs",
"env_logger",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"getrandom",
Update lockfile
2020-08-20 18:48:35 -05:00
"libc",
"log",
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
"measureme",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"rand",
Update lockfile
2020-08-20 18:48:35 -05:00
"rustc-workspace-hack",
"rustc_version",
"shell-escape",
Initial data-race detector, passes all current tests but additional tests are required
2020-11-01 18:23:27 -06:00
"smallvec",
add lockfile
2019-10-14 02:38:08 -05:00
]
bump miri dependencies
2021-04-04 04:45:09 -05:00
[[package]]
name = "num_cpus"
version = "1.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
dependencies = [
"hermit-abi",
"libc",
]
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "parking_lot"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.11.2"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "7d17b78036a60663b797adeaee46f5c9dfebb86948d1255007a1d6be0271ff99"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
dependencies = [
"instant",
"lock_api",
"parking_lot_core",
]
[[package]]
name = "parking_lot_core"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.8.5"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "d76e8e1493bcac0d2766c42737f34458f1c8c50c0d23bcb24ea953affb273216"
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
dependencies = [
"cfg-if",
"instant",
"libc",
"redox_syscall",
"smallvec",
"winapi",
]
[[package]]
name = "perf-event-open-sys"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ce9bedf5da2c234fdf2391ede2b90fabf585355f33100689bc364a3ea558561a"
dependencies = [
"libc",
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "ppv-lite86"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.15"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "ed0cfbc8191465bed66e1718596ee0b0b35d5ee1f41c5df2189d0fe8bde535ba"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "proc-macro2"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.33"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "fb37d2df5df740e582f28f8560cf425f52bb267d872fe58358eadb554909f07a"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"unicode-xid",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "quote"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.10"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "38bc8cc6a5f2e3655e0899c1b848643b2562f853f114bfec7be120678e3ace05"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"proc-macro2",
add lockfile
2019-10-14 02:38:08 -05:00
]
'cargo update' all the things
2021-04-04 04:11:19 -05:00
[[package]]
name = "rand"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.8.4"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "2e7573632e6454cf6b99d7aac4ccca54be06da05aca2ef7423d22d27d4d4bcd8"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
dependencies = [
"libc",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"rand_chacha",
"rand_core",
"rand_hc",
'cargo update' all the things
2021-04-04 04:11:19 -05:00
]
[[package]]
name = "rand_chacha"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.3.1"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
dependencies = [
"ppv-lite86",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"rand_core",
'cargo update' all the things
2021-04-04 04:11:19 -05:00
]
[[package]]
name = "rand_core"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.6.3"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "d34f1408f55294453790c48b2f1ebbb1c5b4b7563eb1f418bcfcfdbb06ebb4e7"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"getrandom",
'cargo update' all the things
2021-04-04 04:11:19 -05:00
]
[[package]]
name = "rand_hc"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.3.1"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "d51e9f596de227fda2ea6c84607f5558e196eeaf43c986b724ba4fb8fdf497e7"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"rand_core",
add lockfile
2019-10-14 02:38:08 -05:00
]
'cargo update' all the things
2021-04-04 04:11:19 -05:00
[[package]]
name = "redox_syscall"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.10"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "8383f39639269cde97d255a32bdb68c047337295414940c68bdd30c2e13203ff"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
dependencies = [
"bitflags",
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "redox_users"
bump miri dependencies
2021-04-04 04:45:09 -05:00
version = "0.4.0"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump miri dependencies
2021-04-04 04:45:09 -05:00
checksum = "528532f3d801c87aec9def2add9ca802fe569e44a544afe633765267840abe64"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"getrandom",
"redox_syscall",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "regex"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.5.4"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "d07a8629359eb56f1e2fb1652bb04212c072a87ba68546a04065d525673ac461"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"aho-corasick",
"memchr",
"regex-syntax",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "regex-syntax"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.6.25"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "f497285884f3fcff424ffc933e56d7cbca511def0c9831a7f9b5f6153e3cc89b"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "remove_dir_all"
cargo update main crates
2020-09-17 13:08:18 -05:00
version = "0.5.3"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update main crates
2020-09-17 13:08:18 -05:00
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "rustc-workspace-hack"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "fc71d2faa173b74b232dedc235e3ee1696581bb132fc116fa3626d6151a1a8fb"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "rustc_version"
Update dependencies
2021-10-01 16:08:58 -05:00
version = "0.4.0"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies
2021-10-01 16:08:58 -05:00
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"semver",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "rustfix"
cargo update
2020-04-10 03:28:23 -05:00
version = "0.5.1"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "f2c50b74badcddeb8f7652fa8323ce440b95286f8e4b64ebfd871c609672704e"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"anyhow",
"log",
"serde",
"serde_json",
add lockfile
2019-10-14 02:38:08 -05:00
]
bump miri dependencies
2021-04-04 04:45:09 -05:00
[[package]]
name = "rustversion"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.6"
bump miri dependencies
2021-04-04 04:45:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "f2cc38e8fa666e2de3c4aba7edeb5ffc5246c1c2ed0e3d17e560aeeba736b23f"
bump miri dependencies
2021-04-04 04:45:09 -05:00
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "ryu"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.9"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "73b4b750c782965c211b42f022f59af1fbceabdd026623714f104152f1ec149f"
add lockfile
2019-10-14 02:38:08 -05:00
Add `measureme` integration for profiling the interpreted program This PR uses the `measureme` crate to profile the call stack of the program being interpreted by Miri. This is accomplished by starting a measureme 'event' when we enter a function call, and ending the event when we exit the call. The `measureme` tooling can be used to produce a call stack from the generated profile data. Limitations: * We currently record every single entry/exit. This might generate very large profile outputs for programs with a large number of function calls. In follow-up work, we might want to explore sampling (e.g. only recording every N function calls). * This does not integrate very well with Miri's concurrency support. Each event we record starts when we push a frame, and ends when we pop a frame. As a result, switching between virtual threads will cause events from different threads to be interleaved. Additionally, the recorded for a particular frame will include all of the work Miri does before that frame completes, including executing another thread. The `measureme` integration is off by default, and must be enabled via `-Zmiri-measureme=<output_name>`
2021-05-08 11:20:51 -05:00
[[package]]
name = "scopeguard"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "semver"
Update dependencies
2021-10-01 16:08:58 -05:00
version = "1.0.4"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies
2021-10-01 16:08:58 -05:00
checksum = "568a8e6258aa33c13358f81fd834adb854c6f7c9468520910a9b1e8fac068012"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "serde"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.131"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "b4ad69dfbd3e45369132cc64e6748c2d65cdfb001a2b1c232d128b4ad60561c1"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"serde_derive",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "serde_derive"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.131"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "b710a83c4e0dff6a3d511946b95274ad9ca9e5d3ae497b63fda866ac955358d2"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"proc-macro2",
"quote",
"syn",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "serde_json"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.73"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "bcbd0344bc6533bc7ec56df11d42fb70f1b912351c0825ccb7211b59d8af7cf5"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"itoa",
"ryu",
"serde",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "shell-escape"
cargo update main crates
2020-09-17 13:08:18 -05:00
version = "0.1.5"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update main crates
2020-09-17 13:08:18 -05:00
checksum = "45bb67a18fa91266cc7807181f62f9178a6873bfad7dc788c42e6430db40184f"
add lockfile
2019-10-14 02:38:08 -05:00
Initial data-race detector, passes all current tests but additional tests are required
2020-11-01 18:23:27 -06:00
[[package]]
name = "smallvec"
Update dependencies
2021-10-01 16:08:58 -05:00
version = "1.7.0"
Initial data-race detector, passes all current tests but additional tests are required
2020-11-01 18:23:27 -06:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies
2021-10-01 16:08:58 -05:00
checksum = "1ecab6c735a6bb4139c0caafd0cc3635748bbb3acf4550e8138122099251f309"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "syn"
update lockfile
2021-12-14 11:20:03 -06:00
version = "1.0.82"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "8daf5dd0bb60cbd4137b1b587d2fc0ae729bc07cf01cd70b36a1ed5ade3b9d59"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"proc-macro2",
"quote",
"unicode-xid",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "tempfile"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
version = "3.2.0"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
'cargo update' all the things
2021-04-04 04:11:19 -05:00
checksum = "dac1c663cfc93810f88aed9b8941d48cabf856a1b111c29a40439018d870eb22"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"cfg-if",
Update lockfile
2020-08-20 18:48:35 -05:00
"libc",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"rand",
"redox_syscall",
Update lockfile
2020-08-20 18:48:35 -05:00
"remove_dir_all",
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
[[package]]
name = "term"
bump miri dependencies
2021-04-04 04:45:09 -05:00
version = "0.7.0"
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump miri dependencies
2021-04-04 04:45:09 -05:00
checksum = "c59df8ac95d96ff9bede18eb7300b0fda5e5d8d90960e76f8e14ae765eedbf1f"
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"dirs-next",
"rustversion",
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi",
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "termcolor"
rustup + cargo update
2020-12-17 05:53:10 -06:00
version = "1.1.2"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rustup + cargo update
2020-12-17 05:53:10 -06:00
checksum = "2dfed899f0eb03f32ee8c6a0aabdb8a7949659e3466561fc0adf54e26d88c5f4"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi-util",
add lockfile
2019-10-14 02:38:08 -05:00
]
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
[[package]]
name = "tester"
bump miri dependencies
2021-04-04 04:45:09 -05:00
version = "0.9.0"
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump miri dependencies
2021-04-04 04:45:09 -05:00
checksum = "0639d10d8f4615f223a57275cf40f9bdb7cfbb806bcb7f7cc56e3beb55a576eb"
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
dependencies = [
bump miri dependencies
2021-04-04 04:45:09 -05:00
"cfg-if",
Update lockfile
2020-08-20 18:48:35 -05:00
"getopts",
"libc",
bump miri dependencies
2021-04-04 04:45:09 -05:00
"num_cpus",
Update lockfile
2020-08-20 18:48:35 -05:00
"term",
try the stable feature of compiletest
2019-11-16 02:07:35 -06:00
]
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "unicode-width"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.1.9"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "3ed742d4ea2bd1176e236172c8429aaf54486e7ac098db29ffe6529e0ce50973"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "unicode-xid"
update lockfile
2021-12-14 11:20:03 -06:00
version = "0.2.2"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update lockfile
2021-12-14 11:20:03 -06:00
checksum = "8ccb82d61f80a663efe1f787a51b16b5a51e3314d6ac365b08639f52387b33f3"
add lockfile
2019-10-14 02:38:08 -05:00
'cargo update' all the things
2021-04-04 04:11:19 -05:00
[[package]]
name = "wasi"
version = "0.10.2+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fd6fbd9a79829dd1ad0cc20627bf1ed606756a7f77edff7b66b7064f9cb327c6"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "winapi"
cargo update main crates
2020-09-17 13:08:18 -05:00
version = "0.3.9"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update main crates
2020-09-17 13:08:18 -05:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
add lockfile
2019-10-14 02:38:08 -05:00
[[package]]
name = "winapi-util"
cargo update main crates
2020-09-17 13:08:18 -05:00
version = "0.1.5"
add lockfile
2019-10-14 02:38:08 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update main crates
2020-09-17 13:08:18 -05:00
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
add lockfile
2019-10-14 02:38:08 -05:00
dependencies = [
Update lockfile
2020-08-20 18:48:35 -05:00
"winapi",
add lockfile
2019-10-14 02:38:08 -05:00
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update lockfile
2020-08-20 18:48:35 -05:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Reference in New Issue Copy Permalink