public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/101996] libatomic: RISC-V 64: Infinite recursion in __atomic_compare_exchange_1
Date: Fri, 20 Aug 2021 13:47:46 +0000 [thread overview]
Message-ID: <bug-101996-4-862f2Hq8vI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101996-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101996
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
Worksforme:
00000000000029ae <__atomic_compare_exchange_1@@LIBATOMIC_1.0>:
29ae: 0ff0000f fence
29b2: 0005c683 lbu a3,0(a1)
29b6: ff857893 andi a7,a0,-8
29ba: 891d andi a0,a0,7
29bc: 050e slli a0,a0,0x3
29be: 0ff00713 li a4,255
29c2: 0008b783 ld a5,0(a7)
29c6: 00a71733 sll a4,a4,a0
29ca: 00a696b3 sll a3,a3,a0
29ce: 00a61633 sll a2,a2,a0
29d2: fff74e13 not t3,a4
29d6: 00fe7833 and a6,t3,a5
29da: 00f77333 and t1,a4,a5
29de: 00c86833 or a6,a6,a2
29e2: 02d31363 bne t1,a3,2a08
<__atomic_compare_exchange_1@@LIBATOMIC_1.0+0x5a>
29e6: 1008b32f lr.d t1,(a7)
29ea: 00f31663 bne t1,a5,29f6
<__atomic_compare_exchange_1@@LIBATOMIC_1.0+0x48>
29ee: 1908beaf sc.d t4,a6,(a7)
29f2: fe0e9ae3 bnez t4,29e6
<__atomic_compare_exchange_1@@LIBATOMIC_1.0+0x38>
29f6: 40f30833 sub a6,t1,a5
29fa: 879a mv a5,t1
29fc: fc081de3 bnez a6,29d6
<__atomic_compare_exchange_1@@LIBATOMIC_1.0+0x28>
2a00: 0ff0000f fence
2a04: 4505 li a0,1
2a06: 8082 ret
2a08: 00a7d7b3 srl a5,a5,a0
2a0c: 00f58023 sb a5,0(a1)
2a10: 0ff0000f fence
2a14: 4501 li a0,0
2a16: 8082 ret
next prev parent reply other threads:[~2021-08-20 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 12:50 [Bug middle-end/101996] New: " bqq3z3afgj at bcco4 dot anonbox.net
2021-08-20 13:47 ` schwab@linux-m68k.org [this message]
2021-08-21 8:53 ` [Bug middle-end/101996] " bqq3z3afgj at bcco4 dot anonbox.net
2021-08-21 9:08 ` schwab@linux-m68k.org
2021-08-23 23:00 ` wilson at gcc dot gnu.org
2021-08-24 0:01 ` wilson at gcc dot gnu.org
2021-08-25 19:04 ` wilson at gcc dot gnu.org
2021-08-29 14:55 ` bqq3z3afgj at bcco4 dot anonbox.net
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-101996-4-862f2Hq8vI@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: link
Be 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).