public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/31501] _dl_tlsdesc_dynamic_xsavec may clobber %rbx Date: Tue, 19 Mar 2024 02:46:16 +0000 [thread overview] Message-ID: <bug-31501-131-ezO6SsJUj0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31501-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31501 --- Comment #7 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=717ebfa85c8240d32d0d19d86a484c31c55c9617 commit 717ebfa85c8240d32d0d19d86a484c31c55c9617 Author: H.J. Lu <hjl.tools@gmail.com> Date: Mon Mar 18 06:40:16 2024 -0700 x86-64: Allocate state buffer space for RDI, RSI and RBX _dl_tlsdesc_dynamic preserves RDI, RSI and RBX before realigning stack. After realigning stack, it saves RCX, RDX, R8, R9, R10 and R11. Define TLSDESC_CALL_REGISTER_SAVE_AREA to allocate space for RDI, RSI and RBX to avoid clobbering saved RDI, RSI and RBX values on stack by xsave to STATE_SAVE_OFFSET(%rsp). +==================+<- stack frame start aligned at 8 or 16 bytes | |<- RDI saved in the red zone | |<- RSI saved in the red zone | |<- RBX saved in the red zone | |<- paddings for stack realignment of 64 bytes |------------------|<- xsave buffer end aligned at 64 bytes | |<- | |<- | |<- |------------------|<- xsave buffer start at STATE_SAVE_OFFSET(%rsp) | |<- 8-byte padding for 64-byte alignment | |<- 8-byte padding for 64-byte alignment | |<- R11 | |<- R10 | |<- R9 | |<- R8 | |<- RDX | |<- RCX +==================+<- RSP aligned at 64 bytes Define TLSDESC_CALL_REGISTER_SAVE_AREA, the total register save area size for all integer registers by adding 24 to STATE_SAVE_OFFSET since RDI, RSI and RBX are saved onto stack without adjusting stack pointer first, using the red-zone. This fixes BZ #31501. Reviewed-by: Sunil K Pandey <skpgkp2@gmail.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-19 2:46 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 14:23 [Bug dynamic-link/31501] New: " fweimer at redhat dot com 2024-03-16 14:23 ` [Bug dynamic-link/31501] " fweimer at redhat dot com 2024-03-16 14:35 ` fweimer at redhat dot com 2024-03-16 14:48 ` hjl.tools at gmail dot com 2024-03-16 17:05 ` hjl.tools at gmail dot com 2024-03-17 4:00 ` sam at gentoo dot org 2024-03-17 8:12 ` fweimer at redhat dot com 2024-03-17 10:39 ` hjl.tools at gmail dot com 2024-03-17 10:43 ` sam at gentoo dot org 2024-03-17 10:57 ` sam at gentoo dot org 2024-03-17 16:28 ` hjl.tools at gmail dot com 2024-03-19 2:46 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-19 2:46 ` hjl.tools at gmail dot com 2024-03-20 15:37 ` fweimer at redhat dot com 2024-04-02 13:17 ` carlos at redhat dot com 2024-04-03 17:43 ` cvs-commit 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-31501-131-ezO6SsJUj0@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).