mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: musl@lists.openwall.com
Subject: Re: [musl] loongarch64 atomics not working?
Date: Wed, 13 Mar 2024 15:45:31 +0100	[thread overview]
Message-ID: <ZfG8Cycju/0frdQ+@waldemar-brodkorb.de> (raw)
In-Reply-To: <ff727783-6dd4-a4a5-f177-5dd2b791fa9e@loongson.cn>

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

  reply	other threads:[~2024-03-13 14:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  0:51 Rich Felker
2024-03-12  2:06 ` Hongliang Wang
2024-03-12  8:31   ` lixing
2024-03-12 16:18     ` Waldemar Brodkorb
2024-03-12 16:47       ` Thorsten Glaser
2024-03-12 17:18         ` Waldemar Brodkorb
2024-03-13  1:42           ` lixing
2024-03-13 14:45             ` Waldemar Brodkorb [this message]
2024-03-13 14:52               ` Rich Felker
2024-03-14  5:44                 ` Waldemar Brodkorb
2024-03-14  6:45                   ` lixing
2024-03-14 13:44                     ` Leah Neukirchen
2024-03-15  0:58                       ` lixing
2024-03-12  8:48   ` Jingyun Hua

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=ZfG8Cycju/0frdQ+@waldemar-brodkorb.de \
    --to=wbx@openadk.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).