From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Protected Objects and Interrupt Handlers Date: Thu, 25 Feb 2016 16:02:09 +0000 Organization: A noiseless patient Spider Message-ID: References: <7663896a-a15e-47fd-8c7e-54a1c20d8d0f@googlegroups.com> <2922ffdd-9678-4502-9bcb-8b199af91543@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="03d977edd803a9f1bf346d48fa393156"; logging-data="2748"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Om5mIzh1Y1oWx1H4nCdpNeSzG92Xo170=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Cancel-Lock: sha1:ZeLs4RZ68JZMaS+KWgvzkrSsJW4= sha1:wylCmi3SvcoDUjYjN00Ctn05Qy4= Xref: news.eternal-september.org comp.lang.ada:29606 Date: 2016-02-25T16:02:09+00:00 List-Id: Maciej Sobczak writes: > Last but no least - Simon has pointed you towards an article (a book > chapter, in fact) where the interrupts are handled by regular > procedures instead - as an author of that text I feel responsible for > clarifying why - the reason is that the book consistently assumes a > zero-runtime execution platform, where the necessary scaffolding for > protected objects (namely: actual synchronization) simply does not > exist. A minor point: a common cited advantage of the Cortex series is that ISRs can be written in ordinary code, without compiler magic. This seems to imply that other MCUs _do_ need compiler magic!