bump rustc, llvm #348
No reviewers
Labels
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/artiq-zynq#348
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "srenblad/artiq-zynq:bump_to_llvm13"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps to 1.56.0-nightly (29ef6cf16 2021-08-31) and LLVM13.
Tested on Kasli-SoC in standalone and master-satellite configs with basic blinky. MonInj tested in master-sat. Analyzer tested on standalone.
Ran HITL tests for standalone, no issues. Performance tests are comparable to before bump.
@ -59,6 +61,7 @@ impl Write for Cursor<&mut [u8]> {
let data = &mut self.inner[self.pos..];
let len = buf.len().min(data.len());
for i in 0..len {
unsafe { asm!("", options(preserves_flags, nostack, readonly)); }
I think we can get rid of this hack altogether since memory is copied elsewhere when accessing the DRTIO aux buffers?
But this could be another PR.
Are subkernels tested?
@ -21,3 +21,3 @@
log_buffer = { version = "1.2" }
crc = { version = "1.7", default-features = false }
core_io = { version = "0.1", features = ["collections"] }
core_io = { git = "https://git.m-labs.hk/M-Labs/rs-core_io.git", rev = "e9d3edf027", features = ["collections"] }
What does that patch do?
core_io
is unmaintained and locked to the rustc versions already supported due to how the repo is maintained using scripts and patches fromstd::io
. It is probably the biggest blocker for bumping the rust version, due to also being a dependency ofrust-fatfs
inzynq-rs
.Tested the simple subkernel example from the manual, blinking the satellite LEDs, message passing and preloading.