From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, FROM_LOCAL_NOVOWEL,HEADER_FROM_DIFFERENT_DOMAINS,HK_RANDOM_FROM, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id 2F03623497 for ; Mon, 6 May 2024 19:36:19 +0200 (CEST) Received: (qmail 17430 invoked by uid 550); 6 May 2024 17:36:13 -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 16371 invoked from network); 6 May 2024 17:36:12 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715016964; x=1715621764; darn=lists.openwall.com; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=JMeCpct7v5Jttlx+Sxpw52CEUXhSS9v5m8iaL/Cw1qk=; b=TAs5wVMoAtqjwS69lst54f8QckqZ50htnTxpAT6Ps/EYowZHbiwHp0FC12zCWnNTUO p0xJd6uw5FK+fBQ94Lh8q+vHKCLvwFqXJztBreDPXAaacAhMAnGekAy7tvt084pC2GKa AZVDlTiqBNKqoXXM/Pc5CWZeAXR0ErmB6UQIeiL/p3rw94CO3dIju7hG4D5Gtu2rpaAI ZyshcUx5Qa4YJdVyfPzAVYMAHA9OMO1+yS32G4MY6RgFsvg9QpmAg/VnsvfKncC+idVk aShre4v3fBGn1Mt8Ramrir95RrUs+kIJTeLebrBO+VP+Qgecw+91XmcMM9T1j58s5nP3 o4ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715016964; x=1715621764; 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=JMeCpct7v5Jttlx+Sxpw52CEUXhSS9v5m8iaL/Cw1qk=; b=ahJhi8p9L+nepaxvu8mEhckndwEe5wIXXXMk/IgJKOSG1PKL9cDVruvi7GtcIm3Y2H /n5o9b1hNfcM79+RhDbJBzHX4URDMAS+BwI9uOYPk0yKy95K8H5Y0b2JuD8ElR/LXOyS WN8KN5MRRQgGtjsBVYJXNAaOV/Rw3n93bJ3dTMigf67LYXZRuKXSyCC5RAXa7Hm5FqDi c3PLkiJCTeFacXXc/8wl0AGG/8i/mHDZirFky+qharXmV0E7GsR3JnqJDfUQBwqvI/lD oHo/FMmGynwr1UoHjUztgF7iNgYHHaFOKWks1HVVN3Ba70LhJ7iLzPg9UwAAyIavm6LX FGkw== X-Gm-Message-State: AOJu0YwpW9decWyATizMC3MP8MDXqjR1VjzbiIk9fTmPu2WOvVfU6qt/ DsNcfQNgkmJ2uZm+Gb/sCpv2dZbfdSmShwgrZlWi8HchcFmD3VMzzajEIwvU3TaD7pn4FtrpPel 6mGCi/m5S5kHUOIvCfByGy4yKEjo= X-Google-Smtp-Source: AGHT+IGxnLVgMZPeQ7TWOPN/wbGjL3Z4fK7KxrYPASBOhGQZLqodpzDyuy7sZJ6KfFJPwiRis9xrjPOuctOuGGN92LQ= X-Received: by 2002:a17:90a:ee89:b0:2b2:827f:4652 with SMTP id i9-20020a17090aee8900b002b2827f4652mr10392838pjz.6.1715016963430; Mon, 06 May 2024 10:36:03 -0700 (PDT) MIME-Version: 1.0 References: <20240329014824.GG32430@brightrain.aerifal.cx> <20240403205555.GO4163@brightrain.aerifal.cx> <20240403214555.GP4163@brightrain.aerifal.cx> <20240404140134.GQ4163@brightrain.aerifal.cx> <20240404150053.GR4163@brightrain.aerifal.cx> <20240408144107.GV4163@brightrain.aerifal.cx> <20240408153244.GW4163@brightrain.aerifal.cx> <20240506144814.GF10433@brightrain.aerifal.cx> In-Reply-To: <20240506144814.GF10433@brightrain.aerifal.cx> From: Max Filippov Date: Mon, 6 May 2024 10:35:52 -0700 Message-ID: To: Rich Felker Cc: musl@lists.openwall.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [musl] [RFC v2 0/2] xtensa FDPIC port Hi Rich, On Mon, May 6, 2024 at 7:47=E2=80=AFAM Rich Felker wrote: > Ping. Did this help with the xtensa fdpic work? yeah, I think I've fixed all the issues raised in this review. I've made an FDPIC ABI specification for xtensa and tried to get feed from the Cadence Tensilica folks, but so far (4 weeks later) only got a few questions, like "is there a plan to support windowed ABI" and "why a11 is chosen as a GOT pointer". The spec is available here: https://github.com/jcmvbkbc/xtensa-abi/blob/master/fdpic-xtensa.txt its current version is 1. I wonder if there's a place where I could post it for a wider review? I've updated the toolchain components to match the spec and support both musl and uclibc-ng with single source. There are still some issues in the binutils (e.g. static PIE support in the linker is broken ATM) and in the compiler (libstdc++ build is broken for the uclibc-ng due to dl_iterate_phdr interface difference), but none of it is directly related t= o the xtensa port for musl. libc-test results when running in the QEMU linux-user emulation are the following: FAIL src/functional/pthread_mutex_pi-static.exe [status 1] FAIL src/functional/pthread_mutex_pi.exe [status 1] FAIL src/functional/pthread_robust-static.exe [timed out] FAIL src/functional/pthread_robust.exe [timed out] FAIL src/functional/strptime-static.exe [status 1] FAIL src/functional/strptime.exe [status 1] FAIL src/math/acoshl.exe [status 1] FAIL src/math/asinhl.exe [status 1] FAIL src/math/erfcl.exe [status 1] FAIL src/math/fma.exe [status 1] FAIL src/math/fmal.exe [status 1] FAIL src/math/lgammal.exe [status 1] FAIL src/math/tgammal.exe [status 1] FAIL src/regression/pthread-robust-detach-static.exe [status 1] FAIL src/regression/pthread-robust-detach.exe [status 1] mutex_pi and robust list failures are QEMU-linux-user specific and they pass in system emulation and math test failures are due to the ULP differences. I haven't had a chance to look at the strptime failures, but IIRC they're also failing for the sh port. The testing uncovered the following two issues in the QEMU-linux-user emulation: https://mail.gnu.org/archive/html/qemu-devel/2024-03/msg06891.html https://mail.gnu.org/archive/html/qemu-devel/2024-03/msg06892.html I will post v3 shortly. --=20 Thanks. -- Max