From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 Received: (qmail 30459 invoked from network); 15 Apr 2020 18:26:34 -0000 Received-SPF: pass (mother.openwall.net: domain of lists.openwall.com designates 195.42.179.200 as permitted sender) receiver=inbox.vuxu.org; client-ip=195.42.179.200 envelope-from= Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with UTF8ESMTPZ; 15 Apr 2020 18:26:34 -0000 Received: (qmail 1984 invoked by uid 550); 15 Apr 2020 18:26:32 -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 1965 invoked from network); 15 Apr 2020 18:26:32 -0000 Date: Wed, 15 Apr 2020 14:26:19 -0400 From: Rich Felker To: sidneym@codeaurora.org, musl@lists.openwall.com Message-ID: <20200415182619.GI11469@brightrain.aerifal.cx> References: <000a01d61328$7f2614b0$7d723e10$@codeaurora.org> <20200415163015.GG11469@brightrain.aerifal.cx> <029101d6134e$56d4ece0$047ec6a0$@codeaurora.org> <20200415180620.GA23945@port70.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200415180620.GA23945@port70.net> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Hexagon DSP support On Wed, Apr 15, 2020 at 08:06:20PM +0200, Szabolcs Nagy wrote: > * 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? > > i'd look at the pthread failures first. If qemu-user these would possibly be expected failures. If qemu-system or native they almost surely indicate bugs in the atomics. > sqrt/sqrtf should work too (you may want to > implement them if there is a single instruction) > other math failures are not target specific. > the ipc failures may be relevant, or it > may be a time issue (if timestamps fail). arch/hexagon/bits is missing sem.h etc. so it's using the arch/generic definitions, which only work for archs that are 64-bit or where the only existing kernel interface has 64-bit time_t (i.e. riscv32). For anything else they must be defined with the proper hi/lo time members, and bits/ipcstat.h must define IPC_STAT as 0x102 to activate the translations. > > 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] Could you send the whole src/REPORT file which contains not just the FAIL lines but the specific test failures that caused them? And label whether it's for qemu-user, qemu-system, or real metal. Rich