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=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,3025dd6d917b499c X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Received: by 10.66.80.8 with SMTP id n8mr6001045pax.17.1351478372105; Sun, 28 Oct 2012 19:39:32 -0700 (PDT) Path: s9ni66459pbb.0!nntp.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!newsreader4.netcologne.de!news.netcologne.de!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Brian Drummond Newsgroups: comp.lang.ada Subject: Re: Ada, the best language with the not-so-best tool chain Date: Wed, 24 Oct 2012 21:17:35 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <38af7fb8-b0a4-4a31-87aa-b7b698cc89c3@googlegroups.com> <1f645050-cf4c-40bf-a797-9687b69e4a54@googlegroups.com> <18ats2960nsvm$.kfufsnul13aq$.dlg@40tude.net> <5072c9ae$0$6562$9b4e6d93@newsspool4.arcor-online.net> <4keoa6epdxt7.1nnwxy7v7ar90.dlg@40tude.net> <5072dc68$0$6554$9b4e6d93@newsspool4.arcor-online.net> <1f7cmfp1l65w1.1deog8cfxbs0u$.dlg@40tude.net> <5072e37a$0$6556$9b4e6d93@newsspool4.arcor-online.net> <1wzhg6cdjkwjj$.uq66rzr2nlgy.dlg@40tude.net> <7xzk3ckxbv.fsf@ruckus.brouhaha.com> <96e29613-fec6-488b-842b-8f5dbcf44a03@googlegroups.com> <7xtxtjvoag.fsf@ruckus.brouhaha.com> <7xk3uflt4b.fsf@ruckus.brouhaha.com> Mime-Version: 1.0 Injection-Date: Wed, 24 Oct 2012 21:17:35 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="0e44dd4a3c4e0a6e83a86f947fb780ae"; logging-data="11977"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Uw0JcEBHF7sR3HNMNcXR+wjrWgHVz42Y=" User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Cancel-Lock: sha1:x/+yAWp1R2+zoJQY6InXBNnT0Cc= X-Received-Bytes: 3812 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: 2012-10-24T21:17:35+00:00 List-Id: On Wed, 24 Oct 2012 09:41:56 -0700, Paul Rubin wrote: > "Yannick Duchêne (Hibou57)" writes: >> Talking about Ravenscar, you may better think of it as a profile, >> while SPARK, as _based_ on an Ada subset. > > As another matter, if GCC can compile C for a given target, is it likely > to be terribly difficult to use GNAT on that target? I'm thinking of > the AVR processors (8-bit) and maybe the TI MSP430 (16 bit). Both of > these work with GCC/GDB. It's not likely to be easy. For the AVR, things were rocky with certain versions of GCC and better with others. However, GCC4.7 builds for AVR with Gnat support relatively easily and seems to work well, and the AVR-Ada runtime (at version 1.2) is very usable. For the MSP, which is not an official GCC target, (the MSP backend is not part of the official gcc tree)... well I plan to try it, but I'm not expecting it to be easy. The sort of things that fail are just down to the extreme complexity of the GCC build process, and the fact that : building with Ada support is fairly well tested, and building with (MSP/ AVR) support is fairly well tested, but building with both together ... you sometimes get the impression you are alone on that path (really basic build failures with quite obscure causes) And there is no equivalent to the AVR-Ada runtime. One would probably have to start a port from scratch, using the AVR one as a guide. (It's not really a *run*time so much as providing compile time support for access to the AVR's peripherals and I/O pins etc...) - Brian