-
Notifications
You must be signed in to change notification settings - Fork 45
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
C2Rust updates / fixes #210
Conversation
Build failures after RIOT-OS#189 show that the test coverage is insufficient to catch C2Rust breakage; this mitigates it by building an example that pulls in much more code.
Hmpf. It's not helping, but not breaking things either :-/ |
This uses a branch of the LLVM PR <immunant/c2rust#693> which fixes C2Rust's issue <immunant/c2rust#692>. Both have been preexisting for a while, but became critical when switching over to the current LLVM version.
It's now not only updating to latest upstream, but to a branch that fixes the concrete issue upstream. I'd leave this as two commits because these can well be understood separately, and that the first passed CI on its own (even though that was only because RISCV was untested at that time; now it should not pass any more thanks to RIOT-OS/RIOT#18654) is good separate information. |
LGTM. Let's wait if the hifive1 rust code is built now |
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.
ACK. rust hifive building and passing now.
bors merge |
Build succeeded:
|
This branch is used for investigating failures encountered after merging #189, in which C2Rust errs internally. Upstream might already have solved it.
This builds on #209.