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.1 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19871 invoked from network); 25 Jun 2022 03:36:36 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 25 Jun 2022 03:36:36 -0000 Received: (qmail 20326 invoked by uid 550); 25 Jun 2022 03:36:33 -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 20290 invoked from network); 25 Jun 2022 03:36:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to; bh=qw+RxtzSvEIhN+TM/ditfblDDy4aBBX6rsP2R7fwtLc=; b=haiB1tbpknlfyVN2E2dzVJ9amIKI2qhcVq0XjPFIDJthRrjWcpnnNWcasDM9sdP7OD fMS7sROG12jIIeH7cHY48M9My/aMhI0yHAoK5J8MfWpG5nmr/HZwrhNXSIe4JDCVa3KW yYJHWz4l68Aj7wKD1HPKFyIBZMf3t3tmihLEqGbNYcuhuayJegbiVk0iSuz/2tJ+eQem NoP31KDG0BK7uyhFvXXSULxmg+DG44TDtybe+hriDyzRFszzyZe2ZxwN57g2kV7q43VJ FJk9p7SZ7g+MT505Gz5xxxng1rYLtpDZLYyVmEKaKexqD6oal5NRpkC2ahkU3JXRy60m XylA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to; bh=qw+RxtzSvEIhN+TM/ditfblDDy4aBBX6rsP2R7fwtLc=; b=0uTERxue9lY0/nJS1bcZfohdSvnpqUa7kqtkkqDb4RBoGrdIiS3dx6LxP9vtDJynzH wOx3Zi+AU1Ak6jSp4GVD5qodqilNihRbdINIkJx6DRipDvPFb6Q8AecXN5Bm4bllthqg 7GOZa018tW7epvCU/qrEQVpQ/wI9zufStYpoJtzZ83Pzb7fRkgnF+4InK9iMCd7BHdSc sZqce96rslnLBjrECHEvquqJAp5O5S60NnKXHtmfRbTdCAbfpHdseh4oNuLAbZdPSlND CsVvQXG6h1yKsTj3oklhDNZc/hGWRs+k4Wg2TqlQu4YCUyOouSEIH8j9yS6QSK1DEU4U 7L2g== X-Gm-Message-State: AJIora9JpQ6MvzyQspuY8TkKMBXDImAodRIR6Vzxe5NmLuMo2ACF/YXn 9b+dOW88wrkqBEvyKZJDJDqtREs46CDuH6v7fqk= X-Google-Smtp-Source: AGRyM1v+F5/f9CyQMDM2vIdLeSXJ1POzvKQoO3UWY73db3RYQ6A5LtL7RgwdzNM3mYa5GdTNAelVANU/i8pLWBZj5vU= X-Received: by 2002:a67:2486:0:b0:354:565c:62ec with SMTP id k128-20020a672486000000b00354565c62ecmr981704vsk.26.1656128180980; Fri, 24 Jun 2022 20:36:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?572X5YuH5YiaKFlvbmdnYW5nIEx1byk=?= Date: Sat, 25 Jun 2022 11:36:09 +0800 Message-ID: To: mesa-dev@lists.freedesktop.org, Musl Content-Type: multipart/alternative; boundary="000000000000ee104005e23d630a" Subject: [musl] Fwd: mesa | Remove USE_ELF_TLS macro (!17213) --000000000000ee104005e23d630a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---------- Forwarded message --------- From: Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi (@zboszor) Date: Sat, Jun 25, 2022 at 12:09 AM Subject: Re: mesa | Remove USE_ELF_TLS macro (!17213) To: Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi commented on a discussion on src/mes= on.build: 152 152 libraries : libgl, 153 153 libraries_private : gl_priv_libs, 154 154 requires_private : gl_priv_reqs, 155 - variables : ['glx_tls=3D@0@'.format(use_elf_tls ? 'yes' : 'no')], 155 + variables : ['glx_tls=3D@0@'.format('yes')], 156 156 ) I don't think it's a good idea to make ELF_TLS unconditionally true. Yocto allows choosing the LIBC at least between GLIBC and MUSL, and Mesa built with TLS crashes under MUSL. See this patch: https://git.openembedded.org/openembedded-core/tree/meta/recipes-graphics/m= esa/files/0002-meson.build-make-TLS-ELF-optional.patch and here TLS is only enabled for GLIBC: https://git.openembedded.org/openembedded-core/tree/meta/recipes-graphics/m= esa/mesa.inc#n92 So I am confused. What's the situation about ELF-TLS support in musl? Is that still broken now? -- =E6=AD=A4=E8=87=B4 =E7=A4=BC =E7=BD=97=E5=8B=87=E5=88=9A Yours sincerely, Yonggang Luo --000000000000ee104005e23d630a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


---------- Forwarded message ---------
From: Zo= lt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi (@zboszor) <gitlab@gitlab.freedesktop.org>
Date: Sa= t, Jun 25, 2022 at 12:09 AM
Subject: Re: mesa | Remove USE_ELF_TLS macro= (!17213)
To: <luoyonggang@g= mail.com>


Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi commente= d on a discussion on src/meson.build:

152 152

=C2=A0 =C2=A0 = =C2=A0libraries : libgl,

153 153

=C2=A0 =C2=A0 =C2=A0librarie= s_private : gl_priv_libs,

154 154

=C2=A0 =C2=A0 =C2=A0require= s_private : gl_priv_reqs,

155

- =C2=A0 =C2=A0variables : [= 9;glx_tls=3D@0@'.format(use_elf_tls ? 'yes' : 'no')],
155

+ =C2=A0 =C2=A0variables : ['glx_tls=3D@0@'.format= ('yes')],

156 156

=C2=A0 =C2=A0)

I don't t= hink it's a good idea to make ELF_TLS unconditionally true.

Yoct= o allows choosing the LIBC at least between GLIBC and MUSL, and Mesa built = with TLS crashes under MUSL.

See this patch: https://git.openembedded.org/op= enembedded-core/tree/meta/recipes-graphics/mesa/files/0002-meson.build-make= -TLS-ELF-optional.patch and here TLS is only enabled for GLIBC: https://git.openembedded.org/openembedded-core/tree/m= eta/recipes-graphics/mesa/mesa.inc#n92

So I am confused. What= 9;s the situation about ELF-TLS support in musl?
Is that still broken no= w?

--
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E6=AD=A4=E8=87=B4
=E7= =A4=BC
=E7=BD=97=E5=8B=87=E5=88=9A
Yours
=C2=A0 =C2=A0 sincerely,<= br>Yonggang Luo
--000000000000ee104005e23d630a--