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 libc/31325] New: mips: clone3 is wrong for o32 Date: Thu, 01 Feb 2024 17:40:10 +0000 [thread overview] Message-ID: <bug-31325-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31325 Bug ID: 31325 Summary: mips: clone3 is wrong for o32 Product: glibc Version: 2.39 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: adhemerval.zanella at linaro dot org CC: drepper.fsp at gmail dot com Target Milestone: --- The mips clone3 (sysdeps/unix/sysv/linux/mips/clone3.S) does not take in consideration that the cprestore might generate the gp save on the stack (so clone3 must allocate some space before issuing the syscall) and $8 is not guarantee by the kABI to be preserved after the syscall. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2024-02-01 17:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-31325-131@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).