Hope I got the right stream.
I get these errors when I'm trying to compile the example code for wasmtime 1.0. I did this like 4 hours ago on my work system and it went fine... I'm not sure what happened. I have less RAM at home, but it doesn't look like the compiler ran out of RAM?
error[E0599]: no method named `class` found for struct `regalloc2::SpillSlot` in the current scope
--> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.88.0/src/machinst/vcode.rs:1021:67
|
1021 | ... debug_assert_eq!(from.class(), to.class());
| ^^^^^ method not found in `regalloc2::SpillSlot`
error[E0599]: no method named `class` found for struct `regalloc2::SpillSlot` in the current scope
--> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.88.0/src/machinst/vcode.rs:1029:55
|
1029 | ... debug_assert_eq!(from.class(), to.class());
| ^^^^^ method not found in `regalloc2::SpillSlot`
For more information about this error, try `rustc --explain E0599`.
The following warnings were emitted during compilation:
warning: Failed to run `rustfmt` on ISLE-generated code: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }
warning: Failed to run `rustfmt` on ISLE-generated code: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }
warning: Failed to run `rustfmt` on ISLE-generated code: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }
error: could not compile `cranelift-codegen` due to 2 previous errors
I even removed all the code from main just to be safe:
use anyhow::Result;
use wasmtime::*;
fn main() -> Result<()> {
Ok(())
}
I'm pretty sure I'm on the newest stable rustc. Wasmtime doesn't need nightly, right?
stable-x86_64-unknown-linux-gnu (default)
rustc 1.63.0 (4b91a6ea7 2022-08-08)
Hi, yep, this was actually a mistaken publish of a minor-version update of regalloc2 that should have been a semver bump. I'm yanking the version (0.3.3) now. Sorry about that!
(I just yanked it; try again?)
How do I get regalloc2=0.3.3 out of my Cargo.lock file?
ah I think it was "Cargo update". I had been trying "upgrade".
you can delete that stanza? or git reset --hard HEAD
if you have a git-checkout
I hadn't been using Git yet, and if I delete that stanza it just comes back. I think my cargo had cached the idea that 0.3.3 is the best / newest regalloc
Yep cargo update
dropped it from 0.3.3 to 0.3.2.
Now I'm only getting an error because I forgot to add anyhow
. And I can fix that. Thanks!
ok cool, sorry about the trouble and thanks for letting us know!
Reactor Scram has marked this topic as resolved.
Last updated: Nov 22 2024 at 17:03 UTC