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

>>>>> On Tue, 24 Aug 2021, WANG Xuerui wrote:

> 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

Patch for eselect included below.

From a49477f39d3f000cc2ca57f18aafbd66656aba05 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <ulm@gentoo.org>
Date: Tue, 24 Aug 2021 14:13:08 +0200
Subject: [PATCH] Recognise loongarch*/loong in package-manager lib
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* libs/package-manager.bash.in (arch): Recognise loongarch*/loong.

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 ChangeLog                    | 4 ++++
 libs/package-manager.bash.in | 3 ++-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index dfdfe47..f2ea0b6 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2021-08-24  Ulrich Müller  <ulm@gentoo.org>
+
+	* libs/package-manager.bash.in (arch): Recognise loongarch*/loong.
+
 2021-02-17  Ulrich Müller  <ulm@gentoo.org>
 
 	* modules/news.eselect (do_list): Recognise "new" and "all"
diff --git a/libs/package-manager.bash.in b/libs/package-manager.bash.in
index 35a1e11..c32fcb4 100644
--- a/libs/package-manager.bash.in
+++ b/libs/package-manager.bash.in
@@ -1,5 +1,5 @@
 # -*-eselect-*-  vim: ft=eselect
-# Copyright (c) 2005-2020 Gentoo Authors
+# Copyright (c) 2005-2021 Gentoo Authors
 #
 # This file is part of the 'eselect' tools framework.
 #
@@ -76,6 +76,7 @@ arch() {
 			hppa*)  	ret=hppa	;;
 			i?86)   	ret=x86 	;;
 			ia64*)  	ret=ia64	;;
+			loongarch*)	ret=loong	;;
 			m68k*)  	ret=m68k	;;
 			mips*)  	ret=mips	;;
 			nios2)  	ret=nios2	;;
-- 
2.33.0



  reply	other threads:[~2021-08-24 12:17 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
2021-08-24 12:17               ` Ulrich Mueller [this message]
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=usfyz11g6@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=i.gentoo@xen0n.name \
    /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