From: kaz Kojima <kkojima@rr.iij4u.or.jp>
To: libc-hacker@sources.redhat.com
Subject: [PATCH] SH: fix pread/pwrite (Was: architecture status, please)
Date: Thu, 20 Feb 2003 04:51:00 -0000 [thread overview]
Message-ID: <200302200451.h1K4pGH21904@r-rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Thu, 20 Feb 2003 12:02:34 +0900" <200302200254.h1K2s2H29319@r-rr.iij4u.or.jp>
Hi,
This is a patch for syscall ABI fixing of pread/pread64/pwrite/pwrite64
on SH linux target. Kernel folks took the MIPS's way.
Regards,
kaz
--
2003-02-20 Kaz Kojima <kkojima@rr.iij4u.or.jp>
* sysdeps/unix/sysv/linux/sh/pread.c: New file.
* sysdeps/unix/sysv/linux/sh/pread64.c: Likewise.
* sysdeps/unix/sysv/linux/sh/pwrite.c: Likewise.
* sysdeps/unix/sysv/linux/sh/pwrite64.c: Likewise.
diff -u3prN ORIG/libc/sysdeps/unix/sysv/linux/sh/pread.c LOCAL/libc/sysdeps/unix/sysv/linux/sh/pread.c
--- ORIG/libc/sysdeps/unix/sysv/linux/sh/pread.c Thu Jan 1 09:00:00 1970
+++ LOCAL/libc/sysdeps/unix/sysv/linux/sh/pread.c Thu Feb 20 13:19:20 2003
@@ -0,0 +1 @@
+#include <sysdeps/unix/sysv/linux/mips/pread.c>
diff -u3prN ORIG/libc/sysdeps/unix/sysv/linux/sh/pread64.c LOCAL/libc/sysdeps/unix/sysv/linux/sh/pread64.c
--- ORIG/libc/sysdeps/unix/sysv/linux/sh/pread64.c Thu Jan 1 09:00:00 1970
+++ LOCAL/libc/sysdeps/unix/sysv/linux/sh/pread64.c Thu Feb 20 13:19:20 2003
@@ -0,0 +1 @@
+#include <sysdeps/unix/sysv/linux/mips/pread64.c>
diff -u3prN ORIG/libc/sysdeps/unix/sysv/linux/sh/pwrite.c LOCAL/libc/sysdeps/unix/sysv/linux/sh/pwrite.c
--- ORIG/libc/sysdeps/unix/sysv/linux/sh/pwrite.c Thu Jan 1 09:00:00 1970
+++ LOCAL/libc/sysdeps/unix/sysv/linux/sh/pwrite.c Thu Feb 20 13:19:20 2003
@@ -0,0 +1 @@
+#include <sysdeps/unix/sysv/linux/mips/pwrite.c>
diff -u3prN ORIG/libc/sysdeps/unix/sysv/linux/sh/pwrite64.c LOCAL/libc/sysdeps/unix/sysv/linux/sh/pwrite64.c
--- ORIG/libc/sysdeps/unix/sysv/linux/sh/pwrite64.c Thu Jan 1 09:00:00 1970
+++ LOCAL/libc/sysdeps/unix/sysv/linux/sh/pwrite64.c Thu Feb 20 13:19:20 2003
@@ -0,0 +1 @@
+#include <sysdeps/unix/sysv/linux/mips/pwrite64.c>
next prev parent reply other threads:[~2003-02-20 4:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 22:41 architecture status, please Ulrich Drepper
2003-02-19 23:03 ` Franz Sirl
2003-02-20 2:54 ` kaz Kojima
2003-02-20 4:51 ` kaz Kojima [this message]
2003-02-20 5:32 ` [PATCH] SH: fix pread/pwrite (Was: architecture status, please) Ulrich Drepper
2003-02-20 8:25 ` architecture status, please Andreas Jaeger
2003-02-25 14:15 ` Andreas Jaeger
2003-02-25 14:17 ` Jakub Jelinek
2003-02-20 19:35 ` Richard Henderson
2003-02-21 7:25 ` Richard Henderson
2003-02-20 21:12 ` Philip Blundell
2003-02-25 8:37 ` unwind info fix for ia64 David Mosberger
2003-02-27 9:33 ` Ulrich Drepper
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=200302200451.h1K4pGH21904@r-rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=libc-hacker@sources.redhat.com \
/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).