Daniel Egger
Daniel Egger
> Because you are not 100% sure whether you inlining it is better or not -- that's the job of LLVM. What you want to be sure of is that...
The main aspect here is respecting the declared wish of the developer: if a function is declared `#[ramfunc]` it has to go to RAM, the way to ensure that is...
Sweet! Thank you so much @japaric. That works an absolute treat and has reduced the time to handle an interrupt (including instrumentation so I can measure it but excluding the...
It would be even nicer if we could directly jump into the function in RAM via the interrupt/exception vector rather than have an entry point to an exception handler then...
> Interrupt table should also be in RAM in this case. 🤔
> @therealprof you can put the vector table in RAM but you need to adjust the VTOR register accordingly. I'm not working too much with Cortex-M4... ;)
I haven't seen a M0/M0+ device that had it implemented at least. I do have plenty of M3 and higher devices, too but I haven't looked too deeply into those...
> Problem is, you can't write a lot of Rust code without running into a call to some function that I don't control and thus can't slap a link_section onto....
@jonas-schievink I do not agree with the "unsound" part of your intro but it would certainly be nice to have it.
In general I think we should do this. I'm a bit wary about overboard though, it should still be simply enough to follow what's going on and not require a...