| Age | Commit message (Collapse) | Author |
|---|
|
#1840
kernel32.AddVectoredExceptionHandler -> ntdll.RtlAddVectoredExceptionHandler
kernel32.RemoveVectoredExceptionHandler -> ntdll.RtlRemoveVectoredExceptionHandler
kernel32.ExitProcess -> ntdll.RtlExitUserProcess
kernel32.InitializeCriticalSection -> ntdll.RtlInitializeCriticalSection
kernel32.EnterCriticalSection -> ntdll.RtlEnterCriticalSection
kernel32.LeaveCriticalSection -> ntdll.RtlLeaveCriticalSection
kernel32.DeleteCriticalSection -> ntdll.RtlDeleteCriticalSection
kernel32.TryAcquireSRWLockExclusive -> ntdll.RtlTryAcquireSRWLockExclusive
kernel32.AcquireSRWLockExclusive -> ntdll.RtlAcquireSRWLockExclusive
kernel32.ReleaseSRWLockExclusive -> ntdll.RtlReleaseSRWLockExclusive
kernel32.WakeConditionVariable -> ntdll.RtlWakeConditionVariable
kernel32.WakeAllConditionVariable -> ntdll.RtlWakeAllConditionVariable
kernel32.HeapReAlloc -> ntdll.RtlReAllocateHeap
kernel32.HeapAlloc -> ntdll.RtlAllocateHeap
|
|
rename Cancelled to Canceled
|
|
std: Introduce `Io` Interface
|
|
sigreturn and rt_sigreturn are distinct syscalls on PowerPC.
|
|
tracked by https://github.com/ziglang/zig/issues/25734
|
|
|
|
After handling any signal on x86, it would previously segfault.
|
|
There was a missing parameter.
|
|
fixes start logic for checking whether IO/POLL exist
|
|
missing a call to wToPrefixedFileW
|
|
it disagrees with posix msghdr
|
|
Microsoft documentation says "The if_nametoindex function is implemented
for portability of applications with Unix environments, but the
ConvertInterface functions are preferred."
This was also the only dependency on iphlpapi.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- ILSEQ -> error.BadPathName
- implement dirStatPath for WASI
|
|
|
|
|
|
|
|
got the build runner compiling
|
|
glibc and linux kernel use size_t for some field lengths while POSIX and
musl use int. This bug would have caused breakage the first time someone
tried to call sendmsg on a 64-bit big endian system when linking musl
libc.
my opinion:
* msghdr.iovlen: kernel and glibc have it right. This field should
definitely be size_t. With int, the padding bytes are wasted for no
reason.
* msghdr.controllen: POSIX and musl have it right. 4 bytes is plenty for
the length, and it saves 4 bytes next to flags.
* cmsghdr.len: POSIX and musl have it right. 4 bytes is plenty for the
length, and it saves 4 bytes since the other fields are also 32-bits
each.
|
|
|
|
The one about INT_MAX is self-evident from the type system.
The one about kernel having bad types doesn't seem accurate as I checked
the source code and it uses size_t for all the appropriate types,
matching the libc struct definition for msghdr and msghdr_const.
|
|
This "fix" is too opinionated to belong here. Better instead to
document the pitfalls.
|
|
|
|
Turns out Linux on PA-RISC does system calls in a pretty fascinating way; see
arch/parisc/kernel/syscall.S for details.
|
|
|
|
Implemented according to glibc because I'm pretty sure musl gets it wrong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
`std`: some miscellaneous inline asm fixes for mips, mips64, mipsn32, and x32
|
|
windows: Always try using POSIX_SEMANTICS/etc for rename/delete
|
|
I'm not sure why this was here, but this is only a thing on O32, not N32/N64.
|
|
ref https://github.com/ziglang/zig/issues/22189
|
|
ref https://github.com/ziglang/zig/issues/22189
|
|
MIPS I has load hazards so we need to insert nops in a few places. This is not a
problem for MIPS II and later.
While doing this, I also touched up all the inline asm to use ABI register
aliases and a consistent formatting convention. Also fixed a few places that
didn't properly check if the syscall return value should be negated.
|
|
Otherwise, the field names in std.posix.timeval vary by target os.
I think this was an accidental change during the work of #25610
|
|
`std.os.linux`: some miscellaneous cleanup in arch bits
|
|
The compile-time check against the minimum version here wasn't appropriate, since it still makes sense to try using FILE_RENAME_INFORMATION_EX even if the minimum version is something like `xp`, since that doesn't rule out the possibility of the compiled code running on Windows 10/11. This compile-time check was doubly bad since the default minimum windows version (`.win10`) was below the `.win10_rs5` that was checked for, so when providing a target like `x86_64-windows-gnu` it'd always rule out using this syscall.
After this commit, we always try using FILE_RENAME_INFORMATION_EX and then let the operating system tell us when some aspect of it is not supported. This allows us to get the benefits of these new syscalls/flags whenever it's actually possible.
The possible error returns were validated experimentally:
- INVALID_PARAMETER is returned when the underlying filesystem is FAT32
- INVALID_INFO_CLASS is returned on Windows 7 when trying to use FileRenameInformationEx/FileDispositionInformationEx
- NOT_SUPPORTED is returned on Windows 10 >= .win10_rs5 when setting a bogus flag value (I used `0x1000`)
|
|
|
