Jake Goulding

> AVR can be made the default target. @dylanmckay I'm not sure that there's much of a point to this. Rust defaults to the host system, and I'm 99.9999% sure...

> once I get the latest compiler version working We've merged @TimNN's upgrades to LLVM 8, so now might be a good time to give it a shot!

> are we even loading globals correctly now? No, I don't think we are, but I think that responsibility is outside of the compiler proper. I have some old hacked...

> Do you know if this functionality is a part of the CRT? I *think* so, but to be honest I don't fully recall and I'm not even sure I...

> specification itself is always identical across devices I'm not sure that I fully agree with that, as I'm pretty sure mine are different from what most other people use...

> the corresponding C code produces what I would expect Can you try with Clang? That would help decide where to focus.

Great! That means that the problem is "just" in the LLVM backend! 😜I think the next steps would be [to produce a minimal testcase](https://github.com/avr-rust/rust/wiki) of the LLVM IR. Once this...

> Is there some writing-LLVM-IR library that both Clang and rustc use? Not to my knowledge, or at least nothing that wouldn't be in LLVM itself. > `%struct.T* byval` Isn't...

> Isn't that saying it takes a pointer to a struct T by value, not the struct itself by value? Never mind me, my brain mixed up which behavior you...

Here's some random thoughts: x86 might have some extra LLVM optimization passes — not sure where to check for that, or which passes (if any) are run before the LLVM...