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=-3.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE 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 EB0D623EC5 for ; Wed, 13 Mar 2024 15:45:45 +0100 (CET) Received: (qmail 30248 invoked by uid 550); 13 Mar 2024 14:41:29 -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 30212 invoked from network); 13 Mar 2024 14:41:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openadk.org; s=2022; t=1710341131; bh=PyTiKfM2PasBAO+aDWNmaNrb9XObSMN0mCv5v4+eedM=; h=Date:From:To:Subject:References:In-Reply-To:From; b=piUyJPug80p8aNF7ds/fnYmnKKmn16fpObbhRNqhN3+gN3fbNwG3+cIINDzYEo8Ub bxsBHs5va4p9gcXVOtFNqWifZYWUlbnsVIvCLHlAWuKgs8jSqiKblBhY70LkevPHp9 hHAROfcDBi86+sEVb9GmIVrFvqcAHBfIh5b4jnsi4EQgxbqkkQangrB6xkEMwz6jjM X3wRhl+08U+Dy5utDazLkF34/BE04ZJEjX3L15espdp1x0KUvn4nTd4z+jt3M9bwt9 pK9i2TALE/lCf1HQH6AOmovbtBDn8umnrdNDV730koF+Jr5kQAL8bHkU1c1HGyJZ3S 4IdPoi8yDaz7Q== Date: Wed, 13 Mar 2024 15:45:31 +0100 From: Waldemar Brodkorb To: musl@lists.openwall.com Message-ID: References: <20240312005150.GB4163@brightrain.aerifal.cx> <4f5abddd-09f9-f05f-6cc6-719fc365b449@loongson.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: Linux 5.10.0-27-amd64 x86_64 Subject: Re: [musl] loongarch64 atomics not working? Hi, lixing wrote, > > 在 2024/3/13 上午1:18, Waldemar Brodkorb 写道: > > Hi Thorsten, > > Thorsten Glaser wrote, > > > > > Waldemar Brodkorb dixit: > > > > > > > lixing wrote, > > > > > We've tested static and dynamic build mksh with commit id > > > > > cbb8a0196aab53165a35339fd91ade599d184f both works ok. > > > That’s great to hear! > > > > > > > Can you check with qemu-system-loongarch64? I use gcc 13.2.0, > > > > binutils 2.42 and Linux 6.6.18 with the defconfig provided. > > > > Qemu is also 8.2.2. Can you provide your QEMU_EFI.fd for download? > > I just only use qemu user mode, but my colleague give me the address for > download the EFI as follow > > https://github.com/lixianglai/LoongarchVirtFirmware. > > Also, can you post the qemu-system-loongarch64 startup command to me? > > > > Perhaps to distinguish between emulation/runtime and toolchain > > > faults you could send each other the mksh binaries (if statically > > > linked, otherwise probably them plus musl’s dynamic parts)? > > I update the static binary to my repo on github, you can download and try, > we both tested with real hardware > > and qemu-loongarch64 user mode is ok.  This mksh built with gcc 13.2.1, > binutils 2.42, linux 6.6.15 in the loongarch environment. > > https://github.com/lixing-star/binarys > > > Statically linked mksh from me is here: > > https://debug.openadk.org/mksh > we've tested your binary on 3c5000  is ok, but  hanged with > qemu-loongarch64. Are you cross compiled the mksh for use? Yes I do. I found the reason why my mksh didn't worked. I compiled everything with -Os and then I get the deadlock. When I compile everything with -O2 musl mksh is working. So it seems some gcc problem code compiled with -Os. best regards Waldemar