-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Rust base (9th June) (fb7cca33f) #144
Conversation
250fe58
to
a6e4f32
Compare
I can successfully compile |
599edbe
to
261895f
Compare
This commit fixes debug printing of function pointers on AVR. AVR does not support `addrspacecast` instructions, and so this patch modifies libcore so that a `ptrtoint` IR instruction is used and the address space cast is avoided.
Add extra steps for macOS, as noted in #131
261895f
to
c7eb39c
Compare
As far as I'm concerned, that's our current "golden master", so I'd be OK "merging" this as our master branch once we've made sure it compiles on at least a second machine (is the current CI enough for that?) |
@shepmaster, I can test compile my HAL crates with it tomorrow if you want |
@shepmaster the CI run successfully ran |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything seems to work as it should! 👍
FWIW, I can compile my AVR-GCC-free blink example just fine as well! |
hmm, i updated my avr-rust installation, and now my projects fail to build
Any idea what might have gone wrong? |
There certainly isn't a std crate for AVR: no filesystem, no threads, etc. I don't know how your code could have been compiling before. Unless build scripts use the host system's libstd, in which case it seems like your build might not be complete. Did you try deleting the build artifacts and doing a clean build? Are you following the instructions in the README? |
Of course the project itself isn't using |
I suggest deleting |
Deleted .xargo and the whole compiler and built it again, the problem seems to persist. |
@peacememories: You are probably using rustup, right? Which directory did you link the toolchain to, using |
|
Try linking against |
linking against stage2 works. huh. I could've sworn the docs say you should link against stage1? |
Thanks anyway, now I can continue working :) |
huh. I would have sworn that I used stage1 (and I likely wrote the README), but I do have it set to stage2 as well:
I'll change that in the readme. |
Evidently there's some difference, see #144 (comment)
FWIW, I've never installed Rust using this mechanism in the 4 years I've been using it; I always use my local builds right out of the build directory. I kind of regret that we have it in our README at all. |
Darn, I was just about to send you a pull-request with updated instructions :D |
Evidently there's some difference, see avr-rust#144 (comment)
Evidently there's some difference, see avr-rust#144 (comment)
Evidently there's some difference, see #144 (comment)
I've rebased the #137 branch one more time to bring it two months forward - from April to June.