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 libc/28223] mips: clone does not align stack Date: Tue, 14 Dec 2021 22:18:40 +0000 [thread overview] Message-ID: <bug-28223-131-yOmgqU5IkJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28223-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28223 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.34/master branch has been updated by Aurelien Jarno <aurel32@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7af07fe795f43e53d31be1c6f9adba7e05f87b0b commit 7af07fe795f43e53d31be1c6f9adba7e05f87b0b Author: Xi Ruoyao <xry111@mengyan1223.wang> Date: Thu Aug 12 20:31:59 2021 +0000 mips: align stack in clone [BZ #28223] The MIPS O32 ABI requires 4 byte aligned stack, and the MIPS N64 and N32 ABI require 8 byte aligned stack. Previously if the caller passed an unaligned stack to clone the the child misbehaved. Fixes bug 28223. (cherry picked from commit 1f51cd9a860ee45eee8a56fb2ba925267a2a7bfe) -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-12-14 22:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-12 16:37 [Bug libc/28223] New: " xry111 at mengyan1223 dot wang 2021-08-12 20:32 ` [Bug libc/28223] " cvs-commit at gcc dot gnu.org 2021-08-12 20:34 ` jsm28 at gcc dot gnu.org 2021-12-14 22:18 ` cvs-commit 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-28223-131-yOmgqU5IkJ@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).