9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: adr <adr@SDF.ORG>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Aarch64 on labs|9legacy?
Date: Fri, 20 May 2022 21:25:55 +0000 (UTC)	[thread overview]
Message-ID: <b716ba10-accc-d9a9-254-a4813097d8@SDF.ORG> (raw)
In-Reply-To: <CAOw7k5i7h+MxghkGWomroYmuq__vRAYr93QZuUtME0Vjy-msKg@mail.gmail.com>

On Fri, 20 May 2022, Charles Forsyth wrote:

> Date: Fri, 20 May 2022 21:34:05 +0100
> From: Charles Forsyth <charles.forsyth@gmail.com>
> Reply-To: 9fans <9fans@9fans.net>
> To: 9fans <9fans@9fans.net>
> Subject: Re: [9fans] Aarch64 on labs|9legacy?
> 
> It's called arm64

From https://developer.arm.com/documentation/den0024/a/Introduction?lang=en

"AArch64 is the name used to describe the 64-bit execution state
of the ARMv8 architecture. AArch32 describes the 32-bit execution
state of the ARMv8 architecture, which is almost identical to ARMv7.
GNU and Linux documentation (except for Redhat and Fedora distributions)
sometimes refers to AArch64 as ARM64."

I would agree that you could use the therm ARM64 as a synonym of
Aarch64, but giving me just that response... It isn't even funny.

adr.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T000c7f7d66260ba3-M5cf852a151255c694f902925
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-05-20 21:26 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 [this message]
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
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=b716ba10-accc-d9a9-254-a4813097d8@SDF.ORG \
    --to=adr@sdf.org \
    --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).