public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hejinyang at loongson dot cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107713] New: Wrong implementation atomic_exchange<short> on LoongArch Date: Wed, 16 Nov 2022 03:07:34 +0000 [thread overview] Message-ID: <bug-107713-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107713 Bug ID: 107713 Summary: Wrong implementation atomic_exchange<short> on LoongArch Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hejinyang at loongson dot cn Target Milestone: --- Created attachment 53905 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53905&action=edit preprocessed file Target: loongarch64-unknown-linux-gnu Configured with: ../configure --prefix=/usr --libdir=/usr/lib64 --build=x86_64-cross-linux-gnu --host=loongarch64-unknown-linux-gnu --target=loongarch64-unknown-linux-gnu --enable-__cxa_atexit --enable-threads=posix --with-system-zlib --enable-libstdcxx-time --enable-checking=release --with-build-sysroot=/opt/mylaos/sysroot --enable-default-pie --enable-languages=c,c++,fortran,objc,obj-c++,lto gcc version 13.0.0 20220801 (experimental) (GCC) test_of_sync_lock_test_and_set.c: char lock; char hello() { return __sync_lock_test_and_set (&lock, 1); } Cmdline: gcc test_of_sync_lock_test_and_set.c -S --save-temps Output Fragment: 1: ll.w $r12,$r16,0 and $r19,$r12,$r14 bne $r19,$r15,2f <--- Wrong and $r19,$r12,$r17 or $r19,$r19,$r18 sc.w $r19,$r16,0 beq $zero,$r19,1b b 3f 2: dbar 0x700 3:
next reply other threads:[~2022-11-16 3:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 3:07 hejinyang at loongson dot cn [this message] 2022-11-16 7:14 ` [Bug target/107713] " hejinyang at loongson dot cn 2022-11-16 11:27 ` xry111 at gcc dot gnu.org 2022-11-16 11:31 ` xry111 at gcc dot gnu.org 2022-11-16 11:48 ` xry111 at gcc dot gnu.org 2022-11-18 7:05 ` cvs-commit at gcc dot gnu.org 2022-11-18 9:01 ` xry111 at gcc dot gnu.org 2022-11-18 9:13 ` chenglulu at loongson dot cn 2022-11-19 12:37 ` cvs-commit at gcc dot gnu.org 2022-11-19 12:38 ` xry111 at gcc dot gnu.org 2022-11-19 12:39 ` xry111 at gcc dot gnu.org 2022-11-20 3:56 ` chenglulu at loongson dot cn
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=bug-107713-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).