----------------------------------------------------------------------------------
@MSGID: 1@rasp.pasdenom.info>
60cf78d2
@REPLY: 1@dont-email.me> 33d29b8e
@REPLYADDR DrPi <314@drpi.fr>
@REPLYTO 2:5075/128 DrPi
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
1@rasp.pasdenom.info>
@RFC-References: 1@dont-email.me>
1@dont-email.me> 1@dont-email.me> <lyr0mimnup.fsf@pushface.org>
1@rasp.pasdenom.info> <lyil7um345.fsf@pushface.org> 1@rasp.pasdenom.info>
1@dont-email.me> 1@dont-email.me>
@TZUTC: 0200
@PID: Mozilla Thunderbird
@TID: FIDOGATE-5.12-ge4e8b94
> WRT energy use. I use a low power run feature on the STM32L4 which means
> the
> system clock speed can change at any time. That seems to be incompatible
> with any runtime that I have seen except the minimal light-cortex-m4 one. I
> assume working with clocks is more scalable than working with runtimes but
> I do not know for sure.
>
The fact that the clock speed is hard coded is a design choice.
It simplifies the time management.
It makes the runtime more "hard real time" compliant since there are
less computations to be done at execution.
--- Mozilla Thunderbird
* Origin: <
https://pasdenom.info/news.html> (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441