public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/31372] _dl_tlsdesc_dynamic doesn't preserve all caller-saved registers Date: Thu, 11 Apr 2024 19:06:14 +0000 [thread overview] Message-ID: <bug-31372-131-VneC63BTAR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31372-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31372 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |2.40 --- Comment #15 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- Fixed on 2.40. The x86 fixes are 0aac205a814a8511e98d02b91a8dc908f1c53cde, 9b7091415af47082664717210ac49d51551456ab, and 717ebfa85c8240d32d0d19d86a484c31c55c9617; while arm32 is fixed by 64c7e344289ed085517c2227d8e3b06388242c13 (along with other commits for the test infrastructure). The aarch64 implementation already handle the required caller-saved registers. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-11 19:06 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-11 23:04 [Bug dynamic-link/31372] New: _dl_tlsdesc_dynamic doesn't preserve vector registers hjl.tools at gmail dot com 2024-02-11 23:05 ` [Bug dynamic-link/31372] " hjl.tools at gmail dot com 2024-02-11 23:18 ` hjl.tools at gmail dot com 2024-02-12 6:59 ` fw at deneb dot enyo.de 2024-02-12 7:11 ` sam at gentoo dot org 2024-02-12 10:46 ` fweimer at redhat dot com 2024-02-12 13:10 ` hjl.tools at gmail dot com 2024-02-14 15:04 ` [Bug dynamic-link/31372] _dl_tlsdesc_dynamic doesn't preserve all caller-saved registers hjl.tools at gmail dot com 2024-02-14 21:09 ` ismail at i10z dot com 2024-02-15 12:13 ` hjl.tools at gmail dot com 2024-02-15 20:39 ` hjl.tools at gmail dot com 2024-02-15 20:40 ` sam at gentoo dot org 2024-02-15 20:44 ` hjl.tools at gmail dot com 2024-02-15 21:07 ` sam at gentoo dot org 2024-02-15 21:14 ` hjl.tools at gmail dot com 2024-02-28 17:05 ` cvs-commit at gcc dot gnu.org 2024-02-29 12:31 ` cvs-commit at gcc dot gnu.org 2024-03-20 15:37 ` fweimer at redhat dot com 2024-04-02 13:16 ` carlos at redhat dot com 2024-04-03 17:42 ` cvs-commit at gcc dot gnu.org 2024-04-03 17:43 ` cvs-commit at gcc dot gnu.org 2024-04-11 19:06 ` adhemerval.zanella at linaro dot 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-31372-131-VneC63BTAR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).