mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [RFC v2 0/2] xtensa FDPIC port
Date: Thu, 28 Mar 2024 19:01:16 -0400	[thread overview]
Message-ID: <20240328230116.GM4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20240328200319.4016902-1-jcmvbkbc@gmail.com>

On Thu, Mar 28, 2024 at 01:03:17PM -0700, Max Filippov wrote:
> Hello,
> 
> this is the second RFC version of the xtensa FDPIC port for musl.
> There are two patches: the first adds the port and will likely not
> change in the future versions. The second adds two bits of
> xtensa-specific GOT initialization for compatibility with the current
> binutils/gcc and will go away once binutils and gcc are changed to do
> local references differently.
> 
> The following binutils and gcc branches can be used to build the
> xtensa-linux-muslfdpic toolchain:
> 
>   https://github.com/jcmvbkbc/binutils-gdb-xtensa xtensa-2.42-fdpic-musl
>   https://github.com/jcmvbkbc/gcc-xtensa xtensa-14-9655-fdpic-musl
> 
> I've tested this version with libc-test using QEMU linux-user and full
> system emulation. The results in the linux-user are the following:
> 
>   FAIL src/functional/dlopen.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]
> 
> functional/dlopen fails with the
>   src/functional/dlopen.c:39: dlsym main failed: (null)
> There's no failure in the dlsym call, but the pointers don't match.

Is this something related to canonical function descriptors? Is it
musl's fault or a bug in the tooling? I suspect the latter.

> functional/ and regression/ pthread-related failures are expected
> because the robust list functions are not available in the linux-user
> mode. These particular tests pass in full system emulation.
> 
> math tests fail with ULP differences.
> 
> I have also added the following changes to the abi tests to fix the
> build:
> 
> diff --git a/src/api/sys_sem.c b/src/api/sys_sem.c
> index a473cad0a2aa..bd4df9a4fe70 100644
> --- a/src/api/sys_sem.c
> +++ b/src/api/sys_sem.c
> @@ -18,7 +18,11 @@ C(SETALL)
>  {
>  struct semid_ds x;
>  F(struct ipc_perm,sem_perm)
> +#ifdef __xtensa__
> +F(unsigned long, sem_nsems)
> +#else
>  F(unsigned short, sem_nsems)
> +#endif

This is invalid and indicates an error in the port; the whole point of
the tests is to catch that so it can be fixed. POSIX requires
sem_nsems to have type unsigned short. I believe Linux has this wrong
on some (most? all?) archs and we just fix it by replacing the rest
with padding.

Rich

  parent reply	other threads:[~2024-03-28 23:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 20:03 Max Filippov
2024-03-28 20:03 ` [musl] [RFC v2 1/2] xtensa: add port Max Filippov
2024-03-28 20:03 ` [musl] [RFC v2 2/2] WIP xtensa bits Max Filippov
2024-03-28 23:01 ` Rich Felker [this message]
2024-03-29  0:48   ` [musl] [RFC v2 0/2] xtensa FDPIC port Max Filippov
2024-03-29  1:48     ` Rich Felker
2024-04-03  2:30       ` Max Filippov
2024-04-03 20:55         ` Rich Felker
2024-04-03 21:45           ` Rich Felker
2024-04-04  8:44             ` Max Filippov
2024-04-04 14:01               ` Rich Felker
2024-04-04 15:00                 ` Rich Felker
2024-04-08 14:41                   ` Rich Felker
2024-04-08 15:32                     ` Rich Felker
2024-05-06 14:48                       ` Rich Felker
2024-05-06 17:35                         ` Max Filippov
2024-04-04  8:56           ` Max Filippov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240328230116.GM4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).