Matt Waltz
Matt Waltz
@tr1p1ea yes to the struct optimization and any fun new status updates for us :) It's fine to just keep it in this PR
I don't like the fact that some CRT routines are disabling interrupts... but we can't really use them anyway so maybe I'm less conflcted :upside_down_face:
I believe it's been in there almost since the start? Anyway I'm 90% sure it's related to this issue: https://github.com/jacobly0/llvm-project/issues/12
> Are int48_t operation routines available anywhere? `int48_t` is not implemented nor officially supported by the toolchain. I'm not sure what you are doing.
Personally I feel that the firmware linker script should have sections for the stack, heap, and scratch whose sizes are controlled through menuconfig for the platform. What are the thoughts...
> This allows us to use the same FW binary on multiple platforms The same firmware binary doesn't work on multiple platforms though since the platform is responsible for allocating...
You most likely are not using the correct connector.
> Hmm can jacobly launch CI on this or something, to see if it builds as expected? It already built fine on my fork: https://github.com/mateoconlechuga/llvm-project/actions/runs/5039720221/jobs/9038047940
*waits 3 weeks for the merge*
Bump bump 😃