From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 22633 invoked from network); 8 May 2021 19:52:27 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 8 May 2021 19:52:27 -0000 Received: (qmail 26334 invoked by uid 550); 7 May 2021 22:05:45 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 23898 invoked from network); 7 May 2021 21:59:15 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1620424743; bh=etYAHKDMKHHyWPobRrdiE9w2+JL3rKFWKBqQtbHF8XI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=kdCVFJsvfgDFnKhQv/mZ8dOhbqoZRKK2AXe94ffevxWmvUVJmfyz7kB8ltL/Gf+HW GbCaAv5v+CMsp4/jsKU3l/lIFpsb7JPvGoHNCl5Gu0tIXjRWPwyIkKLaujN6m2CHiv xiXC0fmKVcjgrmok/GPjlxY0xvIt26w7e3zvCIaNW9kHCm9CxCaTSZ/BIALOHEuWaI OlG3j1nuOv9yYCBoxGtk50432l8bZpUpWq6ksP3s4uGQIAMVvaVrDOCcBcmq9xqjxa NYrY6Z4C3m79+I1REWLjU538SnX4n0E1JZiS8CYaBiiGBPrJ+SsmvnzAM7sQuNTd+f gnxUBSQRSwi4g== X-Gm-Message-State: AOAM531kg5x1Gcqsp+vtpTpnmlsDdf0Zw22Dc+0nmDEzQ/y3XTcl4eEv tWiavRYCbUvDePVkAJL8uWeysHBnGSGv7lcGSMA= X-Google-Smtp-Source: ABdhPJwB0A1/wGpnMPeUvSvsU+it1GcCDz9YjAnT9U/DUDAbx3UhjK7Y7PCPqFCHfQrLWccVe3rFgdDZ6cXvJeMiR0E= X-Received: by 2002:a05:6830:1b61:: with SMTP id d1mr9983477ote.171.1620424742926; Fri, 07 May 2021 14:59:02 -0700 (PDT) MIME-Version: 1.0 References: <5f6d09a5.c3a.179460eee20.Coremail.zhaixiaojuan@loongson.cn> In-Reply-To: <5f6d09a5.c3a.179460eee20.Coremail.zhaixiaojuan@loongson.cn> From: Arnd Bergmann Date: Fri, 7 May 2021 23:58:15 +0200 X-Gmail-Original-Message-ID: Message-ID: To: musl@lists.openwall.com Cc: =?UTF-8?B?6ZmI5Zu956W6?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [musl] Port the new architecture loongarch64 to musl On Fri, May 7, 2021 at 11:01 AM =E7=BF=9F=E5=B0=8F=E5=A8=9F wrote: > > Hi, > I ported a new architecture loongarch64 on the latest branch of musl mast= er. It has been successfully compiled and run the official test libraries l= ibc-testsuit and libc-test of musl. > The source code of the prot has been published in https://github.com/loon= gson-community/musl. Or check the attachment 0001-port-to-loongarch64.patc= h, it is the transplanted patch file. It's nice to see upstreaming work for loongarch64. I'm mainly interested in the kernel side of this, as I review any new ports of Linux to new architectures. Looking at the system call interfaces, I see that you used the generic ABI, so there is a good chance that this will not require incompatible changes, but a proper review of the kernel port will be necessary to be sure. I did notice that the system call list is a bit outdated and does not reflect the latest kernel, but that should be easy to change. There are a few system ca= lls that are technically obsoleted by newer variants now, and we may decide to drop them for new architectures in favor of the newer variants, e.g. openat= , faccessat, and io_getevents. The order I would generally recommend for upstreaming is: 1. toolchain (either gcc/binutils or clang) 2. kernel 3. libc 4. everything else If you do the order differently, there is a risk that ABI changes in one of= the lower levels require changing the upper levels later on. Arnd