00:17 <re_irc> <James Munns> I've gone mad with power

00:17 <re_irc> <James Munns> pub async fn spawn<F: Future + 'static>(fut: F) {

00:17 <re_irc> let task = Task(MaitakeTask::new(

00:17 <re_irc> &EXECUTOR.scheduler,

00:17 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/d715af30d5e2418dfa9e940460502cc7685502b9e82643e923c9f37a186594f1 (13 lines)

00:17 <re_irc> fut

00:17 <re_irc> <James Munns> oh, wrong room for my shitposts, sorry

19:51 <re_irc> <chemicstry> I did some bare-metal on RPi4 and didn't have any similar issues. Although it was not RPi3 and I was using PL011 uart

20:34 <re_irc> <Catherine> Liam Rosenfeld: are you running PIC code, by any chance?

20:35 <re_irc> <Catherine> "fmt::write" is usually the first time bare-metal and similar code encounters trait objects (and vtables)

20:35 <re_irc> <Catherine> so if your linking is subtly broken it would show up there

20:36 <re_irc> <Catherine> honestly chances are pretty low that it's that, but i'll never forget the several days i spent tracking down a bug in or1k binutils

20:37 <re_irc> <Catherine> could be a bad linker script

20:47 <re_irc> <Liam Rosenfeld> I will look into both of those, thank you. The initialization code I'm currently using is here (https://github.com/liamrosenfeld/rustos/blob/main/kern/src/init/init.s). I ran into an issue earlier with function calls that ended up being because my stack pointer was initialized wrong (the skeleton I'm building off of had "adr sp, _start" but changing it to "ldr sp, =_start" fixed things). I changed that to fix...

20:47 <re_irc> ... that issue but maybe that led to other issues.