From: Rich Felker <dalias@libc.org>
To: sidneym@codeaurora.org
Cc: musl@lists.openwall.com
Subject: Re: [musl][hexagon] testing updates
Date: Wed, 15 Apr 2020 23:16:01 -0400 [thread overview]
Message-ID: <20200416031601.GR11469@brightrain.aerifal.cx> (raw)
In-Reply-To: <093e01d6139c$90bd9da0$b238d8e0$@codeaurora.org>
On Wed, Apr 15, 2020 at 10:10:20PM -0500, sidneym@codeaurora.org wrote:
> Updated alltypes.h.in and added sem.h. This change cleared the following
> errors:
>
> src/functional/pthread_mutex-static.exe
>
> src/functional/pthread_mutex.exe
>
> src/functional/pthread_mutex_pi-static.exe
>
> src/functional/pthread_mutex_pi.exe
> src/functional/sem_init-static.exe
>
> src/functional/sem_init.exe
I'm confused how these changed at all from the changes you made.
sem_init is for POSIX semaphores not sysv ipc ones. The bits/sem.h
things don't have anything to do with it.
> src/regression/pthread_cond-smasher-static.exe
>
> src/regression/pthread_cond-smasher.exe
>
> src/regression/pthread_cond_wait-cancel_ignored-static.exe
>
> src/regression/pthread_cond_wait-cancel_ignored.exe
>
> src/regression/pthread_once-deadlock-static.exe
Likewise these shouldn't have changed either. If they did it's
probably some other hidden state in your test environment.
> The patch is here:
> https://github.com/quic/musl/commit/ca20acd472a8e9e58e584d51c4cd00ced6f37087
The change to alltypes.h.in is wrong. It changes time_t to 32-bit,
which is no longer a supported configuration and not the intent. With
that part reverted and the sysvipc bits headers fixed as described
before, I think you might have it mostly working.
Rich
next prev parent reply other threads:[~2020-04-16 3:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 3:10 sidneym
2020-04-16 3:16 ` Rich Felker [this message]
2020-04-16 16:05 ` sidneym
2020-04-16 16:17 ` 'Rich Felker'
2020-04-17 17:15 ` sidneym
2020-04-17 17:34 ` Rich Felker
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=20200416031601.GR11469@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=sidneym@codeaurora.org \
/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).