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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:3a0d:: with SMTP id m13mr4196282itm.34.1554689588297; Sun, 07 Apr 2019 19:13:08 -0700 (PDT) X-Received: by 2002:a9d:6381:: with SMTP id w1mr16573978otk.314.1554689588046; Sun, 07 Apr 2019 19:13:08 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!136no374657itk.0!news-out.google.com!r82ni552ita.0!nntp.google.com!b2no175910itd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 7 Apr 2019 19:13:07 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=204.27.169.105; posting-account=V8n8rgoAAAAxY-ioSepwPOY8TxGG6wkj NNTP-Posting-Host: 204.27.169.105 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <2d99a259-3288-4981-9bda-97145077a5bd@googlegroups.com> Subject: Understanding GNAT Bare Board Run-time for Cortex-M From: Daniel Way Injection-Date: Mon, 08 Apr 2019 02:13:08 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:56097 Date: 2019-04-07T19:13:07-07:00 List-Id: I'm trying to port the bare-board GNAT run-time to a Coretex-M0+ (NXP KV11Z= 7) processor. I'm new to concurrency and have been reading through the run-= times for the STM32 targets to understand how the tasks and protected objec= ts are implemented, however, there seems to be a web of dependencies betwee= n the different packages and wrappers of wrappers of wrappers for types and= subprograms. * Is there any tool available to scan through the source code and generate = a graphical call graph to help visualize the different dependencies? * Has anyone on the forum successfully ported a bare-board run-time? What w= as your experience and do you have any tips? * Is porting the run-time just a matter of updating the linker, a few packa= ges, and a GPR script, or is there some fundamental implementation changes = to consider? Thank you, Daniel