Cody Schafer

While this would be useful, it's not quite clear to me what the best way to allow both preserving the exact value written to the register & not require that...

archive.org has some snapshots of lan.st: https://web.archive.org/web/20130925191650/http://silverspring.lan.st/ I believe the "libdoc" link contains what you're looking for. That said, it is somewhat out of date. (only up to v5.00)

I'm not aware of any specific restrictions or allowances for the build architectures used in yocto.

Goal here was primarily to form the recipes so that the data for multiple build archs could be defined at once, so we'd have a path to add support for...

This looks like it might be something related to our handling of git deps in combination with `crate` deps. What repo or package is the `vmm` crate being provided by?

I've also seen these zero-sized crates. In my case I've seen it in the do_fetch for rust-native with building `core-image-minimal` with `rustfmt` added as a package.

The inclusion of a `-L */recipe-sysroot/*` arg here is interesting an somewhat unexpected. My first thought here is trying to figure out what is causing it to be included. Options...

I've tried to do this too with the experiment in merging the rust-llvm build into rust. IIRC, it failed there too due to llvm not recognizing the target it was...

One of my nagging suspicions about our use of `-C crate_hash=${BB_TASKHASH}` in `RUSTFLAGS` is that it doesn't necessarily appear to handle the case of 2 versions of the same-named crate...

Alternate to removing entirely is pushing it further down the call chain for crate hash generation so we pick up enough of the hash to include the version number, but...