public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Samuel Thibault <sthibaul@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] hurd: Implement _hurd_longjmp_thread_state for x86_64 Date: Sun, 2 Apr 2023 23:29:00 +0000 (GMT) [thread overview] Message-ID: <20230402232900.982D83858401@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=20427b8f231edfa786cbf2672f8d00199ea7c6c6 commit 20427b8f231edfa786cbf2672f8d00199ea7c6c6 Author: Sergey Bugaev <bugaevc@gmail.com> Date: Sun Mar 19 18:10:11 2023 +0300 hurd: Implement _hurd_longjmp_thread_state for x86_64 Signed-off-by: Sergey Bugaev <bugaevc@gmail.com> Message-Id: <20230319151017.531737-29-bugaevc@gmail.com> Diff: --- sysdeps/mach/hurd/x86_64/longjmp-ts.c | 41 +++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/sysdeps/mach/hurd/x86_64/longjmp-ts.c b/sysdeps/mach/hurd/x86_64/longjmp-ts.c new file mode 100644 index 0000000000..2c57d26aab --- /dev/null +++ b/sysdeps/mach/hurd/x86_64/longjmp-ts.c @@ -0,0 +1,41 @@ +/* Perform a `longjmp' on a Mach thread_state. x86_64 version. + Copyright (C) 1991-2023 Free Software Foundation, Inc. + This file is part of the GNU C Library. + + The GNU C Library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + The GNU C Library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with the GNU C Library; if not, see + <https://www.gnu.org/licenses/>. */ + +#include <hurd/signal.h> +#include <setjmp.h> +#include <jmpbuf-offsets.h> +#include <mach/thread_status.h> + + +/* Set up STATE to do the equivalent of `longjmp (ENV, VAL);'. */ + +void +_hurd_longjmp_thread_state (void *state, jmp_buf env, int val) +{ + struct i386_thread_state *ts = state; + + ts->rbx = env[0].__jmpbuf[JB_RBX]; + ts->rbp = env[0].__jmpbuf[JB_RBP]; + ts->r12 = env[0].__jmpbuf[JB_R12]; + ts->r13 = env[0].__jmpbuf[JB_R13]; + ts->r14 = env[0].__jmpbuf[JB_R14]; + ts->r15 = env[0].__jmpbuf[JB_R15]; + ts->ursp = env[0].__jmpbuf[JB_RSP]; + ts->rip = env[0].__jmpbuf[JB_PC]; + ts->rax = val ?: 1; +}
reply other threads:[~2023-04-02 23:29 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=20230402232900.982D83858401@sourceware.org \ --to=sthibaul@sourceware.org \ --cc=glibc-cvs@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).