Dylan McKay

I guess, in the Crater run, the `no_std` feature of every crate will need to be enabled if it exists, otherwise compilation is impossible.

@pietroalbini that's good to hear, thanks! I will create a DO NOT MERGE PR to upstream Rust including the changes required to run the AVR rustc fork. Do you have...

@japaric those are good suggestions. I've raised avr-rust/rust#125 to track testing of `compiler-builtins`. Unfortunately, we can't use compiler-builtins with AVR yet because the libgcc library from avr-libc contains a few...

I've raised avr-rust/rust#93 to track porting `embedded-hal` to AVR. It's not as high on the priority list compared to LLVM bugs though.

@japaric > In another thread, you asked about having / distributing a bunch of AVR targets / target configuration files that are pretty much the same except for the target-cpu...

@japaric > @dylanmckay out of curiosity do the AVR targets have max-atomic-width set to 0 or to some other value? It is currently the default of `None`, which Rust maps...

@japaric > It is currently the default of None, which Rust maps to the target point width, therefore 16. > > > But does it generate the right thing? Does...

> could you help me identify assembly operations that require inline assemly on AVR I've taken a look over the full instruction set listing, here's what stands out Assembly operations...

That's an interesting point. I like the idea of easily being able to compile all boards. I recently added a `target_cpu` cfg attribute to the AVR rust fork, which can...

> Is there a reason to ever compile anything but the current one? Yes, I want this crate to also be used in tooling. I'd like to write a Rust...