public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: WANG Xuerui <i.gentoo@xen0n.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port
Date: Thu, 12 Aug 2021 09:21:31 +0800	[thread overview]
Message-ID: <4eb1c199-af10-cc46-faf2-5396b2de5f09@xen0n.name> (raw)
In-Reply-To: <YRQTY8P3/LF0RKAP@linux1.home>

On 8/12/21 02:13, William Hubbs wrote:

> On Thu, Aug 12, 2021 at 12:39:33AM +0800, WANG Xuerui wrote:
>> I'm planning to take ARCH=loongarch for the port; and support the LP64 ABI
>> first. I'd like to support both LP64 and ILP32 ABIs, but that's not a
>> priority.
>> The ABI flag might be named "ABI_LOONGARCH" but that's IMO a bit long (pun
>> semi-intended); ARCH=loong and ABI_LOONG might be better, I'm open to
>> suggestions.
> FWIW, I like loong and ABI_LOONG better, or even better would be to use the
> string `uname -m` returns for the hardware as ARCH and as the suffix for
> ABI_.

Ahh I forgot to mention that...

$ uname -m
loongarch64

And the triple is "loongarch64-unknown-linux-gnu"; kernel port sits at 
arch/loongarch; almost everything except Go uses the "loongarch" 
version. Go people didn't like duplicating "arch" for their GOARCH 
value, so it's "GOARCH=loong64" there, otherwise the Loongson people 
pushing their agenda would have used "loongarch64" too.

I would say this is mostly aesthetic matter, because we have equally 
long ARCH names like "microblaze" or "openrisc" too. From a user's 
perspective I'd personally prefer "loong" to save some typing, but 
"loongarch" wouldn't hurt that much either.

>
> William


  reply	other threads:[~2021-08-12  1:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 16:39 [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port WANG Xuerui
2021-08-11 18:13 ` William Hubbs
2021-08-12  1:21   ` WANG Xuerui [this message]
2021-08-12  6:00     ` Michał Górny
2021-08-12  6:39       ` Ulrich Mueller
2021-08-24  3:30         ` WANG Xuerui
2021-08-24  8:46           ` Ulrich Mueller
2021-08-24 10:01             ` WANG Xuerui
2021-08-24 12:17               ` Ulrich Mueller
2021-08-12  9:55 ` Yixun Lan
2021-08-13  5:56   ` WANG Xuerui
2021-10-07 12:46 ` WANG Xuerui

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=4eb1c199-af10-cc46-faf2-5396b2de5f09@xen0n.name \
    --to=i.gentoo@xen0n.name \
    --cc=gentoo-dev@lists.gentoo.org \
    /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