search for: noflag

Displaying 7 results from an estimated 7 matches for "noflag".

Did you mean: oflag
2003 Jun 08
2
sub-directory 'hung' ...
'K, not sure how/what to debug here ... doing a grep of svr1.postgresql.org in /proc/*/status shows all the processes 'stuck' in inode ... /proc/38750/status:inetd 38750 2072 2072 2072 -1,-1 noflags 1055120147,191009 0,0 0,592 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org /proc/38752/status:inetd 38752 2072 2072 2072 -1,-1 noflags 1055120154,886433 0,0 0,637 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org /proc/38753/status:inetd 38753 2072 2072 2072 -1,-1 noflags 1055120155,641964 0,0...
2017 Feb 17
7
RFC: Setting MachineInstr flags through storeRegToStackSlot
...eSetup. This is more invasive, as it will affect all in tree and out-of-tree backends. 3) Add a MachineInstr::MIFlag parameter to storeRegToStackSlot. The storeRegToStackSlot implementation is responsible for applying this flag to all inserted instructions. This could be defaulted to MachineInstr::NoFlags, to minimise changes to function callers, although that defaulted value would have to be replicated in all FooTgtInstrInfo.h headers. For either 2) or 3), the changes are simple, it's just they will affect all backends. I'm very happy to implement the patch, but thought it was worth askin...
2017 Feb 21
3
RFC: Setting MachineInstr flags through storeRegToStackSlot
...e and > > out-of-tree backends. > > > > 3) Add a MachineInstr::MIFlag parameter to storeRegToStackSlot. The > > storeRegToStackSlot implementation is responsible for applying this flag > to > > all inserted instructions. This could be defaulted to > MachineInstr::NoFlags, > > to minimise changes to function callers, although that defaulted value > would > > have to be replicated in all FooTgtInstrInfo.h headers. > > > > For either 2) or 3), the changes are simple, it's just they will affect > all > > backends. I'm very h...
2013 Nov 08
0
[PATCH 2/3] syscalls: Add syscalls needed by arm64
arm64 uses generic syscalls, and does not include the "noat", "noflags", and "deprecated" syscalls. i.e. __ARCH_WANT_SYSCALL_{NO_AT|NO_FLAGS|DEPRECATED} This patch adds the syscalls needed for klibc to run on arm64. Signed-off-by: Steve Capper <steve.capper at linaro.org> --- usr/klibc/Kbuild | 3 +++ usr/klibc/SYSCALLS.def | 33 +++++++...
2013 Nov 12
0
[klibc:master] syscalls: Add syscalls needed by arm64
...t;steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:11 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:13 -0800 [klibc] syscalls: Add syscalls needed by arm64 arm64 uses generic syscalls, and does not include the "noat", "noflags", and "deprecated" syscalls. This patch adds substitution functions for system calls not available on arm64. Originally-by: Neil Williams <codehelp at debian.org> Originally-by: Anil Singhar <anil.singhar at linaro.org> Signed-off-by: Steve Capper <steve.capper at l...
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: