From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-91-241.ec2.internal X-Spam-Level: X-Spam-Status: No, score=0.0 required=3.0 tests=none autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!news.eternal-september.org!paganini.bofh.team!pasdenom.info!.POSTED.2a01:e0a:472:70f0:959e:839e:9b8:b64!not-for-mail From: DrPi <314@drpi.fr> Newsgroups: comp.lang.ada Subject: Re: Should light runtimes get more consideration? Date: Fri, 29 Sep 2023 15:42:17 +0200 Organization: Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 29 Sep 2023 13:42:19 -0000 (UTC) Injection-Info: rasp.pasdenom.info; posting-account="314@usenet"; posting-host="2a01:e0a:472:70f0:959e:839e:9b8:b64"; logging-data="5100"; mail-complaints-to="abuse@pasdenom.info" User-Agent: Mozilla Thunderbird Cancel-Lock: sha256:JAqBKgG/dWEOCJ0IjjZzGlDKznNpTsSaCAiXtw78Ku0= In-Reply-To: Content-Language: en-US Xref: news.eternal-september.org comp.lang.ada:65751 List-Id: > 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.