From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DF3231F44D for ; Mon, 11 Mar 2024 16:10:47 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=WsY9qBQf; dkim-atps=neutral Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 211D1385842C for ; Mon, 11 Mar 2024 16:10:46 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id E68263858D20 for ; Mon, 11 Mar 2024 16:10:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E68263858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org E68263858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710173429; cv=none; b=vvKlHaSo7PBrkW5GsPw87EOLogiv6FBApv60DotA5QrF1xPuWu8McCV1k96QeBraAE8/pnUrlSZ/o7Lm8YpBhddA33DY+51EK3RPEcEVlnr41qI71dBPIqgYUcr9UgyEG2NwBWTPxdj97sJLhW09o7YRaXSIJhS9Q6lNqYfOB/Y= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710173429; c=relaxed/simple; bh=j7xX5UUDXLeccwEwnV56phvc7406qVwBwIECBLW+wzE=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=uzbpjueLRCiHhf6/y3rGdS9PmQEVd71eJJi3r8Cf17t2E1QQgNbydRvzBSy40VPZsWcVGIzzDEsnQOhORJBvvlRynHH3mI8Ed9W9MPIwX7K0pnPLRLMzJzVSwFIpPBjKEOpqHjKTRvLngl8XiUl54pKfqOqtAAFJeYIP5vGVS6g= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710173427; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hY9Vkp6J8iSk9ydF1RJVkek2wlUw1aLk7D6biy0vT2o=; b=WsY9qBQffOz6z+97LcK07W354NuQEnJZhH5q9E7Ap2/TKDiUWk2mbNalWk/81HC3OCQ/Hi XTpZakS72dApibk4m/FM/xqK/k6T9pNrJaZ914CY3D2JOt5WI5mCnLg7tE+ZSLEpLvD6hV 3YLhChiCNCB4P8Vu4fU9ZmH+SuVxPNM= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-543-Gf66stfEOw2iBn0Du3TQiA-1; Mon, 11 Mar 2024 12:10:11 -0400 X-MC-Unique: Gf66stfEOw2iBn0Du3TQiA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 43295803F6D; Mon, 11 Mar 2024 16:10:11 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.78]) by smtp.corp.redhat.com (Postfix) with ESMTPS id F269A10E49; Mon, 11 Mar 2024 16:10:09 +0000 (UTC) From: Florian Weimer To: Joseph Myers Cc: Sergey Bugaev , libc-alpha@sourceware.org, bug-hurd@gnu.org, Adhemerval Zanella Netto , Helmut Grohne Subject: Re: [RFC PATCH 00/23] aarch64-gnu port References: <20240103171502.1358371-1-bugaevc@gmail.com> Date: Mon, 11 Mar 2024 17:10:08 +0100 In-Reply-To: (Joseph Myers's message of "Wed, 3 Jan 2024 17:30:11 +0000 (UTC)") Message-ID: <8734swoilb.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org * Joseph Myers: > On Wed, 3 Jan 2024, Sergey Bugaev wrote: > >> To build this, you need an aarch64-gnu toolchain (binutils, GCC, MIG), >> and GNU Mach headers for AArch64. I have posted the patches for >> binutils, GCC, and GNU Mach to the bug-hurd mailing list; no patches >> are required to build aarch64-gnu-mig. > >> There is no AArch64 port of GNU Mach yet; I'm trying to get the ball >> rolling by making this port of glibc. I have only added some AArch64 > > I think the same principle applies for ports to new (architecture, Hurd) > pairs as for new (architecture, Linux) pairs: the relevant code needs to > be in upstream mainline of all components on which glibc build-depends > before the port can go into glibc (and thus before the symbol versions for > the port can be determined) - and at the point where it's ready to go in, > a corresponding build-many-glibcs.py entry should be added as part of the > patch series. Parts of may > be applicable, though that's more oriented to the case where the > architecture support itself is entirely new. > > You can of course do refactors of existing files not specific to > aarch64-gnu, in preparation for the port, before then, to reduce the size > of the eventual patch series proposing adding the port to glibc. I would like to stress what Joseph says here. You don't need to demonstrate actual usage or something like that, just follow the new port process (upstreamed changes in the glibc build dependencies etc.). Thanks, Florian