9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Arm Thumb compiler for Cortex-M
Date: Fri, 6 Nov 2020 00:58:37 +0000	[thread overview]
Message-ID: <CAOw7k5gCT2wNxK-JWVQ60tVMfSJm8Q9Q2=1Rxso31n=6iivEcQ@mail.gmail.com> (raw)
In-Reply-To: <8DCE6717-CFE8-4281-8ADE-36B263524548@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]

http://vitanuova.com/inferno/downloads.html

On Fri, Nov 6, 2020 at 12:51 AM Don A. Bailey <don.bailey@gmail.com> wrote:

> Where the heck is the inferno tree?
>
> On Nov 5, 2020, at 6:48 PM, Charles Forsyth <charles.forsyth@gmail.com>
> wrote:
>
> 
> tc is different because the register allocation and code generation
> strategies are different from normal ARM
>
> On Fri, Nov 6, 2020 at 12:46 AM Charles Forsyth <charles.forsyth@gmail.com>
> wrote:
>
>> It's utils/tc in the Inferno tree. 5a does both ARM32 and Thumb (because
>> it's abstract assembly), as does 5l.
>>
>> On Fri, Nov 6, 2020 at 12:28 AM Don A. Bailey <don.bailey@gmail.com>
>> wrote:
>>
>>> Any source available?
>>>
>>> On Nov 5, 2020, at 6:11 PM, Charles Forsyth <charles.forsyth@gmail.com>
>>> wrote:
>>>
>>> 
>>> There was a 5[ac] variant for Inferno (ta, tc) that produced Thumb code,
>>> and 5l could link Thumb and ARM32 code.
>>> That wasn't extended once Thumb-2 was issued, since it was
>>> different enough to require a fair amount of work and we had no
>>> immediate application on the Cortex.
>>>
>>>
>>> On Thu, Nov 5, 2020 at 11:38 PM Thaddeus Woskowiak <
>>> tswoskowiak@gmail.com> wrote:
>>>
>>>> I would like to know if anyone is working on or exists an Arm Thumb
>>>> compiler so one could use plan 9 to program Arm Cortex M0/3/4/7
>>>> microcontrollers directly. I know of Charles Forsyth's xc AVR compiler
>>>> which is also interesting. Though I have yet to try it out.
>>>>
>>>> -taw
>>>>
>>>> ------------------------------------------
>>>> 9fans: 9fans
>>>> Permalink:
>>>> https://9fans.topicbox.com/groups/9fans/Tc22ac8ae61456f10-M53d9114f6a2c6402ef14fd63
>>>> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>>>>
>>> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Tc22ac8ae61456f10-M19ec8971e0a6bf813470bdd5>
>

[-- Attachment #2: Type: text/html, Size: 4440 bytes --]

  reply	other threads:[~2020-11-06  0:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 23:36 Thaddeus Woskowiak
2020-11-06  0:10 ` [9fans] " Charles Forsyth
2020-11-06  0:27   ` Don A. Bailey
2020-11-06  0:46     ` Charles Forsyth
2020-11-06  0:47       ` Charles Forsyth
2020-11-06  0:49         ` Don A. Bailey
2020-11-06  0:58           ` Charles Forsyth [this message]
2020-11-06  1:16             ` Don A. Bailey
2020-11-07 14:22   ` Thaddeus Woskowiak
2020-11-07 15:03     ` Charles Forsyth
2020-11-07 21:22       ` Anthony Martin
2020-11-08  1:45         ` Charles Forsyth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOw7k5gCT2wNxK-JWVQ60tVMfSJm8Q9Q2=1Rxso31n=6iivEcQ@mail.gmail.com' \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).