From nobody Sat Jul 27 05:19:25 2024 X-Original-To: dev-commits-src-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WWCbt3gVjz5RNcN for ; Sat, 27 Jul 2024 05:19:38 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: from mail-vk1-f182.google.com (mail-vk1-f182.google.com [209.85.221.182]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WWCbt1NG6z4c84; Sat, 27 Jul 2024 05:19:38 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vk1-f182.google.com with SMTP id 71dfb90a1353d-4f51e80f894so569177e0c.1; Fri, 26 Jul 2024 22:19:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722057577; x=1722662377; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KEZqL5Quqn5PWuKr0io7a0D1nxlVg1kn1GR7m3N6hzo=; b=i3PQSgCs4mimNt4lCnbOHx6mpOEdIVb10gMwjt6ABiXsIPMFtMhEoKn9QEMDGaJ6Pa lWBFCHC5Sj5eWbCRnm9i28RSuuVmsKmCwu5cg24PVqxjw6Po3YL887wiqHyirjwZXzIl Ab+eY2TEXRPbZyMtr7CuHKQYG5gR6Ecw7FLwGSiDiNhrOeD++3Y+Kd/9gLU3iI3J8dHO fa3ryaFxEunmW73KbGS8j+bV6vqi7fMEG6cPKhTbk9/ACZU5GSS4om6ln+RDy4O6QZqx 0OlI84q6rFEk6YQpZY18PEwzxYi4C6plwvT3PwQPmhsGkMD+T3ALO6dSJMK9/5cCXqrT QEgw== X-Forwarded-Encrypted: i=1; AJvYcCXuszBZyyR0iUQszp9mdbOUsPcc9zFcRGMvSFtUBHEpsV3H49Bjcfm8EKqoY1AKxzy3aNfvywHkaBDgaLlSXUiAxHQrkiwV2Y7mwEE6GgXCtIb6M7S8wb7DiGzPXwH7tVxwfdarOswRCmyq7yJ+PwXdZzrdC1W+HIXyPyZ9fX/gPpcrwag= X-Gm-Message-State: AOJu0Yww5/iqPXlJa/lsCVTyLZtb9TVtIt8nAvkH+Doo9Gww1UnpECzN 90emQ5oMfwK4iICqQM77NcwZ9TWQL6hIu1/m8t9mKXQn85CzI+i1t5NvSdmTTwZo6UN8/aRECaK jJ2wAIfdJvrM8q6VExhUagSa8HXU= X-Google-Smtp-Source: AGHT+IFxLG9XUs8u2xqoT0fv35uW+96HJvcVP3bRU0TdxK8EVNVxomvdzqA3DwFozKQqvIvKdIQyPQFYPEyyrN8c7Yg= X-Received: by 2002:a05:6122:2187:b0:4f5:1787:18aa with SMTP id 71dfb90a1353d-4f6e66d915amr2045172e0c.0.1722057577039; Fri, 26 Jul 2024 22:19:37 -0700 (PDT) List-Id: Commit messages for the main branch of the src repository List-Archive: https://lists.freebsd.org/archives/dev-commits-src-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-src-main@freebsd.org Sender: owner-dev-commits-src-main@FreeBSD.org MIME-Version: 1.0 References: <301BF20E-E5D0-401D-805E-F5DF05C73EF4.ref@yahoo.com> <301BF20E-E5D0-401D-805E-F5DF05C73EF4@yahoo.com> <0930E640-9E0E-4E7C-A2BE-C0FD17BB193A@freebsd.org> <9AB648A3-842B-4E94-BA60-952C44A2AE8E@yahoo.com> In-Reply-To: <9AB648A3-842B-4E94-BA60-952C44A2AE8E@yahoo.com> From: Antoine Brodin Date: Sat, 27 Jul 2024 07:19:25 +0200 Message-ID: Subject: Re: git: 5670b8cc3672 - main - libthr: Preresolve selected EABI symbols on arm. To: Mark Millard Cc: Philip Paeps , mmel@freebsd.org, dev-commits-src-main@freebsd.org, "kib@freebsd.org >> Konstantin Belousov" , "imp@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4WWCbt1NG6z4c84 On Sat, Jul 27, 2024 at 6:01=E2=80=AFAM Mark Millard wr= ote: > > > > On Jul 26, 2024, at 20:28, Philip Paeps wrote: > > > On 2024-07-27 07:57:38 (+0800), Mark Millard wrote: > >> Michal Meloun wrote on > >> Date: Thu, 25 Jul 2024 16:25:09 UTC : > >> > >>> The branch main has been updated by mmel: > >>> > >>> URL: https://cgit.FreeBSD.org/src/commit/?id=3D5670b8cc3672d5a6bc2c41= eb48d7d01343c43ad0 > >>> > >>> commit 5670b8cc3672d5a6bc2c41eb48d7d01343c43ad0 > >>> Author: Michal Meloun > >>> AuthorDate: 2024-07-24 15:11:27 +0000 > >>> Commit: Michal Meloun > >>> CommitDate: 2024-07-25 16:24:22 +0000 > >>> > >>> libthr: Preresolve selected EABI symbols on arm. > >>> > >>> Add the ability to pre-resolve architecture-specific EABI symbols = and > >>> use it on arm for selected EABI functions. These functions can be = called > >>> with rtld bind lock write-locked, so they should be resolved in fo= rward. > >>> > >>> Reported by: Mark Millard , John F Carr > >>> Reviewed by: kib, imp > >>> MFC after: 1 week > >>> Differential Revision: https://reviews.freebsd.org/D46104 > >> > >> Philip Paeps is likely going to want to know if any releng/13.* or rel= eng/14.* > >> that would be in some jail(s) on ampere1 or ampere3 will be updated to= have > >> the change. He likely would do a round of updating the jail content vi= ntages > >> in use for any such updated releng/13.* or releng/14.* . > >> > >> So: Any plans to have any already-supported release builds updated? > >> > >> Similarly: What of the upcoming 13.4-RELEASE that has made it to -PRER= ELEASE > >> so far? > >> > >> (I'm not aware of active port building runs based on stable/13 or > >> stable/14 . But, if there are some, they would likely track the MFC up= dates > >> sometime after the MFC update was in place.) > > > > We don't build packages on stable branches. > > Not normally. But there the following existed at one time: > > 14stable-i386-default on beefy11.nyi.freebsd.org > 14stable-amd64-default on beefy12.nyi.freebsd.org > > They may have been very temporary and only for special test > runs for all I know. While the actual build history is gone > now, https://portsfallout.com/server still shows the names > under "build environment". They were temporary when stable/14 was branched and releng/14.0 didn't exis= t yet > > Packages are produced on the earliest supported releng/x branch. > > Yep. My questions for releng/1[34].* do get into what will > be the definition of "supported versions" for at least > armv7. > > The armv7 jails need the fix if they are to avoid being > brittle, which gets into if a EN would be done to change > the definition of "support version" in order to avoid the > armv7 status. The rule about "earliest supported" would > then need to track the update if that gets such an EN > update. > > > I don't actually know how/when the builder jails get upgraded. > > For main to be fixed, the jails have to have been updated. > The host version of main does not (at least relative to > the code at hand). > > For any existing, supported releng/1[34].* to avoid being > brittle like main was, it would need an EN update and > both the base installation and the jails that would then > been intended to have avoided the armv7 status would need > to be updated. > > > That's a question for Antoine (Cc:ed) who manages the actual building. = clusteradm only manages the base installations. The jails track releng branches, so if there is no EN they won't get the f= ix. Antoine > It may be that only main will be fixed unless an example > of the brittle status is observed in some supported > version (or new releng/*.* branch not yet released). > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com