From: Andreas Schwab <schwab@redhat.com>
To: libc-hacker@sourceware.org
Subject: [PATCH] Fix makecontext on s390/s390x
Date: Tue, 13 Apr 2010 16:54:00 -0000 [thread overview]
Message-ID: <m3bpdnpa2c.fsf@hase.home> (raw)
2010-04-13 Andreas Schwab <schwab@redhat.com>
* sysdeps/unix/sysv/linux/s390/s390-32/makecontext.c: Fix setup of
overflow area.
* sysdeps/unix/sysv/linux/s390/s390-64/makecontext.c: Likewise.
---
sysdeps/unix/sysv/linux/s390/s390-32/makecontext.c | 2 +-
sysdeps/unix/sysv/linux/s390/s390-64/makecontext.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/sysdeps/unix/sysv/linux/s390/s390-32/makecontext.c b/sysdeps/unix/sysv/linux/s390/s390-32/makecontext.c
index 94760e0..abe07a0 100644
--- a/sysdeps/unix/sysv/linux/s390/s390-32/makecontext.c
+++ b/sysdeps/unix/sysv/linux/s390/s390-32/makecontext.c
@@ -73,7 +73,7 @@ __makecontext (ucontext_t *ucp, void (*func) (void), int argc, ...)
if (argc > 5) {
sp -= argc - 5;
for (i = 5; i < argc; i++)
- sp[i] = va_arg(ap, long);
+ sp[i - 5] = va_arg(ap, long);
}
va_end (ap);
diff --git a/sysdeps/unix/sysv/linux/s390/s390-64/makecontext.c b/sysdeps/unix/sysv/linux/s390/s390-64/makecontext.c
index b08f1b4..410b021 100644
--- a/sysdeps/unix/sysv/linux/s390/s390-64/makecontext.c
+++ b/sysdeps/unix/sysv/linux/s390/s390-64/makecontext.c
@@ -73,7 +73,7 @@ __makecontext (ucontext_t *ucp, void (*func) (void), int argc, ...)
if (argc > 5) {
sp -= argc - 5;
for (i = 5; i < argc; i++)
- sp[i] = va_arg(ap, long);
+ sp[i - 5] = va_arg(ap, long);
}
va_end (ap);
--
1.7.0.1
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
reply other threads:[~2010-04-13 16:54 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=m3bpdnpa2c.fsf@hase.home \
--to=schwab@redhat.com \
--cc=libc-hacker@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: link
Be 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).