cinap_lenrek ac88ce4f7f make bind(2) error handling consistent ... The mount() and bind() syscalls return -1 on error, and the mountid sequence number on success. The manpage states that the mountid sequence number is a positive integer, but the kernels implementation currently uses a unsigned 32-bit integer and does not guarantee that the mountid will not become negative. Most code just cares about the error, so test for the -1 error value only.		2020-05-02 17:32:01 +02:00
..
5e.c	make bind(2) error handling consistent	2020-05-02 17:32:01 +02:00
arm.c	5e: byte access incorrectly checked for long; brk has to round up addresses	2018-09-28 22:53:24 +00:00
dat.h	5e: approximate LL/SC with cas()	2015-07-07 06:30:34 +02:00
fns.h	5e: implement DSB,DMB,ISB and CLREX instructions	2015-06-19 14:43:32 +02:00
fpa.c	5e: fix amd64	2014-03-08 21:07:57 +01:00
fs.c	updated 5e	2011-06-24 15:10:22 +02:00
mkfile	5e: vfp support	2013-06-11 00:30:16 +05:30
proc.c	5e: make sure stack base is aligned to avoid unaligned memory trap on arm	2015-07-07 06:26:56 +02:00
seg.c	5e: added note support	2011-06-25 16:17:20 +02:00
sys.c	5e: byte access incorrectly checked for long; brk has to round up addresses	2018-09-28 22:53:24 +00:00
util.c	5e: added note support	2011-06-25 16:17:20 +02:00
vfp.c	5e: enable VFP emulation by default, doubles only need to be 4 byte aligned	2015-07-08 02:13:16 +02:00