public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "palmer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104338] New: RISC-V: Subword atomics result in library calls Date: Tue, 01 Feb 2022 23:36:46 +0000 [thread overview] Message-ID: <bug-104338-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338 Bug ID: 104338 Summary: RISC-V: Subword atomics result in library calls Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: palmer at gcc dot gnu.org Target Milestone: --- There's a handful of bugs sort of related to this one, but nothing specific. This has been a long-standing issue and I think folks are generally familiar with it, but just to summarize: we don't have sub-word atomic instruction in RISC-V, so we just call out to the libatomic routines. This causes fallout in a handful of places (see 86005 and 81358, for example) and there's been some attempts to resolve it but nothing appears to have stuck. I figured it'd be a good starter project for Patrick, as he's yet to do any GCC stuff. He's working through it and doesn't have anything to post yet, but figured I'd just open the bug now so folks knew what was going on from our end.
next reply other threads:[~2022-02-01 23:36 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-01 23:36 palmer at gcc dot gnu.org [this message] 2022-02-01 23:41 ` [Bug target/104338] " pinskia at gcc dot gnu.org 2022-02-01 23:41 ` patrick at rivosinc dot com 2022-02-01 23:41 ` pinskia at gcc dot gnu.org 2022-02-02 8:48 ` schwab@linux-m68k.org 2022-02-08 1:08 ` patrick at rivosinc dot com 2022-04-07 14:50 ` i at rvalue dot moe 2022-04-07 14:57 ` palmer at gcc dot gnu.org 2022-04-07 18:29 ` palmer at gcc dot gnu.org 2022-04-08 3:03 ` c141028 at gmail dot com 2022-04-19 17:25 ` patrick at rivosinc dot com 2022-04-19 17:48 ` redi at gcc dot gnu.org 2022-08-16 20:36 ` aurelien at aurel32 dot net 2023-01-26 22:50 ` pinskia at gcc dot gnu.org 2023-01-26 23:30 ` palmer at gcc dot gnu.org 2023-04-12 14:15 ` burnus at gcc dot gnu.org 2023-04-20 16:44 ` patrick at rivosinc dot com 2023-04-26 16:55 ` cvs-commit at gcc dot gnu.org 2023-05-16 17:00 ` cvs-commit at gcc dot gnu.org 2023-05-16 17:04 ` patrick at rivosinc dot com 2023-05-16 19:37 ` aurelien at aurel32 dot net 2023-05-16 19:42 ` i at rvalue dot moe 2023-05-16 20:05 ` palmer at gcc dot gnu.org 2023-10-05 8:47 ` redi at gcc dot gnu.org
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-104338-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).