From: Thaddeus Woskowiak <tswoskowiak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Aarch64 on labs|9legacy?
Date: Sat, 21 May 2022 13:43:53 -0400 [thread overview]
Message-ID: <CAG3JMtaayBGMdqCMfCa9wWKG4+KappCiB9Jr=mkGh_U7kO5HNw@mail.gmail.com> (raw)
In-Reply-To: <38094a4-fe1-5787-8f4e-89f5236d026@SDF.ORG>
On Sat, May 21, 2022 at 1:13 PM adr <adr@sdf.org> wrote:
>
> On Sat, 21 May 2022, Aram H?v?rneanu wrote:
> > Since Charles wrote the arm64 compiler, he can call it whatever he wants.
>
> I wasn't talking about any compiler. Yes, you can call your compiler
> whatever you want. You can call it shitarm, just don't tell me that
> the 64-bit Armv8-A architecture is called that (well, if you were
> used to programming in A32 assembly and now you have to do it in
> A64, I think you could call it _that_).
>
Arm isn't sending you a gift basket of shitty arm computers for
defending their ip. Besides, arm64 is perfectly descriptive vs. Arm's
confusing nomenclature which is just a lazy copy of Intel's iaXX
nomenclature.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T000c7f7d66260ba3-M7b5bbe86b39e7d66ec3a1601
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-21 17:44 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.
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 [this message]
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='CAG3JMtaayBGMdqCMfCa9wWKG4+KappCiB9Jr=mkGh_U7kO5HNw@mail.gmail.com' \
--to=tswoskowiak@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).