public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: WANG Xuerui <i.gentoo@xen0n.name>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port
Date: Tue, 24 Aug 2021 18:01:41 +0800	[thread overview]
Message-ID: <966ac676-9978-ebaa-ef56-92359fdb89b7@xen0n.name> (raw)
In-Reply-To: <uzgt71b7h@gentoo.org>

Hi Ulrich,


On 2021/8/24 16:46, Ulrich Mueller wrote:
>>>>>> On Tue, 24 Aug 2021, WANG Xuerui wrote:
>> It seems the discussion has gone quiet for a while now, so I take that
>> we choose ARCH=loong over ARCH=loongarch according to GLEP 53?
> LGTM
>
>> If that doesn't receive much objection, I'll prepare and send the
>> first few eclass patches soon.
> We also need to update the conditional in eselect:
> https://gitweb.gentoo.org/proj/eselect.git/tree/libs/package-manager.bash.in#n70
Thanks for the reminder!
> Does the GNU triplet (i.e. HOSTTYPE in bash) always use "loongarch"
> literally, or can it have some suffix?

According to their earlier reservation[1] and actual vendor system
behavior, there are 3 possible values:

- loongarch64
- loongarch32
- loongarchx32

Only the LP64 ABI is fully supported by the current upstream submission.
The "loongarch32" thing might NOT be compatible with the LP64 ABI,
instead it might be something embedded-oriented, even instruction
subsets supported might differ. The "loongarchx32" is for an
n32/x32-like ABI that doesn't exist yet, and probably will never get
implemented.

Accordingly, I think we only have to care about "loongarch64" for now.

[1]:
https://git.savannah.gnu.org/gitweb/?p=config.git;a=patch;h=c8ddc8472f8efcadafc1ef53ca1d863415fddd5f



  reply	other threads:[~2021-08-24 10:01 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
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 [this message]
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=966ac676-9978-ebaa-ef56-92359fdb89b7@xen0n.name \
    --to=i.gentoo@xen0n.name \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@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