search for: __m68k__

Displaying 8 results from an estimated 8 matches for "__m68k__".

Did you mean: __i686__
2013 Nov 08
1
[PATCH 2/3] syscalls: Add syscalls needed by arm64
...at(AT_FDCWD, pathname, flags | O_LARGEFILE, mode); } # else extern int openat(int, const char *, int, ...); int open(const char *pathname, int flags, mode_t mode) { return openat(AT_FDCWD, pathname, flags, mode); } # endif #elif _BITSIZE == 32 && !defined(__i386__) && !defined(__m68k__) ... the rest of the current file ...
2016 Apr 13
0
[PATCH 1/1] x32 support
..._BITSIZE == 32 +#if _BITSIZE == 32 && !defined(__x86_64__) extern int __openat(int, const char *, int, mode_t); @@ -35,7 +35,7 @@ int open(const char *pathname, int flags, mode_t mode) #endif /* _BITSIZE == 32 */ -#elif _BITSIZE == 32 && !defined(__i386__) && !defined(__m68k__) +#elif _BITSIZE == 32 && !defined(__i386__) && !defined(__m68k__) && !defined(__x86_64__) extern int __open(const char *, int, mode_t); -- Denis
2013 Nov 12
0
[klibc:master] syscalls: Add syscalls needed by arm64
...LARGEFILE, mode); +} + +#else + +__extern int openat(int, const char *, int, ...); + +int open(const char *pathname, int flags, mode_t mode) +{ + return openat(AT_FDCWD, pathname, flags, mode); +} + +#endif /* _BITSIZE == 32 */ -#if _BITSIZE == 32 && !defined(__i386__) && !defined(__m68k__) +#elif _BITSIZE == 32 && !defined(__i386__) && !defined(__m68k__) extern int __open(const char *, int, mode_t); @@ -19,4 +44,4 @@ int open(const char *pathname, int flags, mode_t mode) return __open(pathname, flags | O_LARGEFILE, mode); } -#endif +#endif /* __NR_open */ d...
2012 Jan 29
5
[PATCH 0/2 v3] mkstemp() and m68k support
Hi, after a year, I decided to hack on klibc again. I?ve reworked both the patch to add mkstemp(), discussing to use AT_RANDOM as cheap entropy source on IRC (if there will ever be another entropy consumer, I can quickly write a minimal arc4random() seeded from it, as it has only 16 octets), capable of making a working mksh (static and shared) on amd64/xen, and the m68k support code, leading to
2012 May 15
5
[PATCH 0/5] resubmitting pending patches
Hi, I?ve gone through the mailing list archives and hereby want to resubmit my pending patches. Most are independent of each other, except the m68k patch which will only be complete if sigsuspend is also fixed. (It can be applied before that, though.) http://www.zytor.com/pipermail/klibc/2012-January/003173.html [PATCH] fix m68k support Resubmitted here as 0005. While there was a question from
2013 Nov 11
5
[PATCH V2 0/3] Introduce arm64 support
Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64
2013 Nov 08
9
[PATCH 0/3] Introduce arm64 support
Hello, This series introduces arm64 support to klibc. I've rebased the work from Neil Williams and Anil Singhar into the following three patches. Most of the code changes are due to new syscall implementations being needed for arm64 as a only a minimal set of syscalls are defined in the arm64 kernel. This series is to be applied against the latest klibc, just after 25a66fa README.klibc:
2010 Jan 28
31
[PATCH 0 of 4] aio event fd support to blktap2
Get blktap2 running on pvops. This mainly adds eventfd support to the userland code. Based on some prior cleanup to tapdisk-queue and the server object. We had most of that in XenServer for a while, so I kept it stacked. 1. Clean up IPC and AIO init in tapdisk-server. [I think tapdisk-ipc in blktap2 is basically obsolete. Pending a later patch to remove it?] 2. Split tapdisk-queue into