public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110061] libatomic: 128-bit atomics should be lock-free on AArch64 Date: Tue, 07 May 2024 07:40:35 +0000 [thread overview] Message-ID: <bug-110061-4-LS8L5cB4ml@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110061-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110061 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|14.0 |14.2 --- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 14.1 is being released, retargeting bugs to GCC 14.2.
prev parent reply other threads:[~2024-05-07 7:40 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 12:46 [Bug target/110061] New: " wilco at gcc dot gnu.org 2023-05-31 12:55 ` [Bug target/110061] " pinskia at gcc dot gnu.org 2023-05-31 12:59 ` pinskia at gcc dot gnu.org 2023-05-31 13:24 ` pinskia at gcc dot gnu.org 2023-05-31 13:59 ` wilco at gcc dot gnu.org 2023-05-31 14:04 ` pinskia at gcc dot gnu.org 2023-05-31 14:06 ` pinskia at gcc dot gnu.org 2023-05-31 14:36 ` wilco at gcc dot gnu.org 2023-06-02 16:02 ` xry111 at gcc dot gnu.org 2023-06-02 17:02 ` wilco at gcc dot gnu.org 2023-06-02 17:49 ` xry111 at gcc dot gnu.org 2023-06-02 20:37 ` wilco at gcc dot gnu.org 2023-06-02 20:41 ` xry111 at gcc dot gnu.org 2023-06-02 20:48 ` wilco at gcc dot gnu.org 2023-06-02 21:23 ` wilco at gcc dot gnu.org 2023-06-04 10:23 ` xry111 at gcc dot gnu.org 2023-12-22 14:38 ` wilco at gcc dot gnu.org 2024-03-18 1:02 ` raj.khem at gmail dot com 2024-03-18 1:06 ` pinskia at gcc dot gnu.org 2024-05-07 7:40 ` rguenth at gcc dot gnu.org [this message]
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-110061-4-LS8L5cB4ml@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).