From: <sidneym@codeaurora.org>
To: <musl@lists.openwall.com>
Subject: RE: [musl] Hexagon DSP support
Date: Wed, 15 Apr 2020 13:22:29 -0500 [thread overview]
Message-ID: <02b601d61352$d3d8b8d0$7b8a2a70$@codeaurora.org> (raw)
In-Reply-To: <20200415180620.GA23945@port70.net>
> -----Original Message-----
> From: Szabolcs Nagy <nsz@port70.net>
> Sent: Wednesday, April 15, 2020 1:06 PM
> To: sidneym@codeaurora.org
> Cc: musl@lists.openwall.com
> Subject: Re: [musl] Hexagon DSP support
>
> * sidneym@codeaurora.org <sidneym@codeaurora.org> [2020-04-15
> 12:50:21 -0500]:
> > > > Recently work has been done with clang/llvm/lld to extend support
> > > > for Qualcomm's Hexagon DSP to a Linux target. At this point the
> > > > publicly available LLVM tools are able to build and run Hexagon
> > > > programs via
> > QEMU.
> ...
> > This is the list, the context associated with some of the failures can
> > be bulky so I hope the summary is ok. Let me know which failures are
> > most critical and I will try to fix those first. 51 failures after
> > removing the
> > TIME64 define
>
> is this qemu system emulation?
No it isn't however that is being worked on.
>
> i'd look at the pthread failures first.
> sqrt/sqrtf should work too (you may want to implement them if there is a
> single instruction) other math failures are not target specific.
In fact that does go away if I used the hardware accelerated routine that is
part of compiler-rt.builtins (__hexagon_sqrt) Creating an explicit
reference to compiler-rt-builtins vs just copying the assembly, which is
preferred?
> the ipc failures may be relevant, or it
> may be a time issue (if timestamps fail).
>
> >
> > FAIL src/api/main.exe [status 1]
> > FAIL src/functional/dlopen.exe [status 1] FAIL
> > src/functional/ipc_msg-static.exe [status 1] FAIL
> > src/functional/ipc_msg.exe [status 1] FAIL
> > src/functional/ipc_sem-static.exe [status 1] FAIL
> > src/functional/ipc_sem.exe [status 1] FAIL
> > src/functional/ipc_shm-static.exe [status 1] FAIL
> > src/functional/ipc_shm.exe [status 1] FAIL
> > src/functional/pthread_mutex-static.exe [status 1] FAIL
> > src/functional/pthread_mutex.exe [status 1] FAIL
> > src/functional/pthread_mutex_pi-static.exe [timed out] FAIL
> > src/functional/pthread_mutex_pi.exe [signal Segmentation fault] FAIL
> > src/functional/pthread_robust-static.exe [timed out] FAIL
> > src/functional/pthread_robust.exe [timed out] FAIL
> > src/functional/sem_init-static.exe [status 1] FAIL
> > src/functional/sem_init.exe [status 1] FAIL
> > src/functional/strptime-static.exe [status 1] FAIL
> > src/functional/strptime.exe [status 1] FAIL
> > src/functional/utime-static.exe [status 1] FAIL
> > src/functional/utime.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/exp2l.exe [status 1] FAIL src/math/fmal.exe [status
> > 1] FAIL src/math/ilogb.exe [status 1] FAIL src/math/ilogbf.exe [status
> > 1] FAIL src/math/ilogbl.exe [status 1] FAIL src/math/lgammal.exe
> > [status 1] FAIL src/math/powf.exe [status 1] FAIL src/math/powl.exe
> > [status 1] FAIL src/math/sqrt.exe [status 1] FAIL src/math/sqrtf.exe
> > [status 1] FAIL src/math/sqrtl.exe [status 1] FAIL src/math/tgamma.exe
> > [status 1] FAIL src/math/tgammaf.exe [status 1] FAIL
> > src/math/tgammal.exe [status 1] FAIL src/math/y0.exe [status 1] FAIL
> > src/math/y0f.exe [status 1] FAIL src/math/y1.exe [status 1] FAIL
> > src/math/y1f.exe [status 1] FAIL src/math/yn.exe [status 1] FAIL
> > src/math/ynf.exe [status 1] FAIL
> > src/regression/malloc-brk-fail-static.exe [status 1] FAIL
> > src/regression/malloc-brk-fail.exe [timed out] FAIL
> > src/regression/pthread-robust-detach-static.exe [status 1] FAIL
> > src/regression/pthread-robust-detach.exe [status 1] FAIL
> > src/regression/pthread_cond-smasher-static.exe [status 1] FAIL
> > src/regression/pthread_cond-smasher.exe [status 1] FAIL
> > src/regression/pthread_cond_wait-cancel_ignored-static.exe [status 1]
> > FAIL src/regression/pthread_once-deadlock-static.exe [status 1]
> >
> >
> > >
> > > Rich
next prev parent reply other threads:[~2020-04-15 18:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 13:19 sidneym
2020-04-15 16:30 ` Rich Felker
2020-04-15 17:50 ` sidneym
2020-04-15 18:06 ` Szabolcs Nagy
2020-04-15 18:22 ` sidneym [this message]
2020-04-16 9:36 ` Szabolcs Nagy
2020-04-16 15:34 ` Rich Felker
2020-04-16 16:26 ` sidneym
2020-04-16 16:34 ` 'Rich Felker'
2020-04-15 18:26 ` Rich Felker
2020-04-15 19:12 ` sidneym
2020-04-15 19:29 ` 'Rich Felker'
2020-04-30 22:44 ` sidneym
2020-04-30 23:51 ` Rich Felker
2020-05-05 23:37 ` sidneym
2020-05-06 0:59 ` Rich Felker
2020-06-18 16:37 ` sidneym
2020-06-18 21:42 ` Szabolcs Nagy
2020-06-19 21:58 ` sidneym
2020-06-19 22:46 ` Rich Felker
2020-06-20 0:03 ` [musl] strtok Robert Skopalík
2020-06-20 0:15 ` Rich Felker
2020-06-20 0:36 ` Robert Skopalík
2020-06-20 0:46 ` Robert Skopalík
2020-06-20 1:44 ` Rich Felker
2020-06-20 7:07 ` Patrick Oppenlander
2020-06-20 13:00 ` Robert Skopalík
2020-06-22 0:57 ` Bery Saidi
2020-06-20 2:29 ` [musl] Hexagon DSP support sidneym
2020-06-20 3:20 ` Rich Felker
2020-07-20 21:26 ` sidneym
2020-07-23 21:56 ` Szabolcs Nagy
2020-07-24 17:49 ` sidneym
2020-09-16 20:49 ` sidneym
2020-09-17 1:32 ` 'Rich Felker'
2020-09-17 22:31 ` sidneym
2020-09-18 1:08 ` Rich Felker
2020-09-18 8:10 ` Szabolcs Nagy
2020-09-20 13:12 ` sidneym
2020-09-20 17:17 ` 'Rich Felker'
2020-09-21 14:09 ` sidneym
2020-04-15 18:55 ` Fangrui Song
2021-03-09 20:25 sidneym
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='02b601d61352$d3d8b8d0$7b8a2a70$@codeaurora.org' \
--to=sidneym@codeaurora.org \
--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).