From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Aarch64 on labs|9legacy?
Date: Sat, 21 May 2022 13:06:13 -0400 [thread overview]
Message-ID: <7397b2cb-f34c-2616-885d-7a311432b103@fjrhome.net> (raw)
In-Reply-To: <0F2A3D329B8F286ABAC1187E73F3D694@eigenstate.org>
The compiler appears to be called 7c.
adr, looking at the original email on this thread, it is not very clear
what you are trying to ask?
On 5/21/22 12:39 PM, ori@eigenstate.org wrote:
> Quoth Aram Hăvărneanu <aram.h@mgk.ro>:
>> Since Charles wrote the arm64 compiler, he can call it whatever he wants.
>>
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaarch64
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T000c7f7d66260ba3-M9469a817902ca1783560b9c7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-21 17:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 19:35 adr
2022-05-20 20:34 ` Charles Forsyth
2022-05-20 21:25 ` adr
2022-05-21 16:13 ` Aram Hăvărneanu
2022-05-21 16:39 ` ori
2022-05-21 17:06 ` Frank D. Engel, Jr. [this message]
2022-05-21 17:53 ` [9fans] Aarch64 on labs|9legacy?jj adr
2022-05-21 18:00 ` Aram Hăvărneanu
2022-05-21 17:15 ` [9fans] Aarch64 on labs|9legacy? adr
2022-05-21 17:11 ` adr
2022-05-21 17:38 ` Aram Hăvărneanu
2022-05-21 18:01 ` adr
2022-05-21 18:04 ` Aram Hăvărneanu
2022-05-22 0:05 ` Dan Cross
2022-05-22 0:26 ` adr
2022-05-22 14:36 ` hiro
2022-05-22 14:43 ` Dan Cross
2022-05-22 16:29 ` hiro
2022-05-21 17:43 ` Thaddeus Woskowiak
2022-05-22 18:18 ` Charles Forsyth
2022-05-22 20:15 ` adr
2022-05-22 20:33 ` Dan Cross
2022-05-22 22:16 ` hiro
2022-05-23 14:41 ` Charles Forsyth
2022-05-22 23:43 adr
2022-05-23 3:02 ` Thaddeus Woskowiak
2022-05-23 11:18 ` adr
2022-05-23 14:15 ` adr
2022-05-23 14:33 ` hiro
2022-05-23 14:37 ` hiro
2022-05-23 14:34 ` hiro
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=7397b2cb-f34c-2616-885d-7a311432b103@fjrhome.net \
--to=fde101@fjrhome.net \
--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).