Alex Rønne Petersen 890433e292
std.os.linux: Define timespec as kernel_timespec (64-bit) for riscv32.
This is kind of a hack because the timespec in UAPI headers is actually still
32-bit while __kernel_timespec is 64-bit. But, importantly, all the syscalls
take __kernel_timespec from the get-go (because riscv32 support is so recent).

Defining our timespec this way will allow all the syscall wrappers in
std.os.linux to do the right thing for riscv32. For other 32-bit architectures,
we have to use the 64-bit time syscalls explicitly to solve the Y2038 problem.
2024-07-29 09:50:41 +02:00
..
2024-07-09 14:25:42 -07:00
2024-07-09 14:25:42 -07:00
2024-07-25 18:52:20 -07:00
2024-07-23 11:43:12 -07:00
2024-03-21 14:11:46 -07:00
2024-02-23 02:37:11 -07:00
2024-07-23 11:43:12 -07:00
2024-07-09 14:25:42 -07:00
2024-07-09 14:25:42 -07:00
2024-07-09 14:25:42 -07:00
2024-07-19 00:30:32 -07:00
2024-03-21 14:11:46 -07:00
2024-07-09 14:25:42 -07:00
2024-07-02 16:31:15 +02:00
2024-03-10 18:13:30 -07:00
2024-03-21 14:11:46 -07:00
2024-07-09 14:25:42 -07:00
2024-07-28 20:40:53 -07:00
2024-07-26 04:05:40 -07:00
2024-07-28 21:34:14 -07:00
2024-03-10 18:13:30 -07:00
2024-07-19 00:30:32 -07:00
2024-05-26 16:13:54 -04:00
2024-03-21 14:11:46 -07:00
2024-07-20 01:06:29 -07:00
2024-02-05 11:55:14 +03:30
2024-07-23 11:43:12 -07:00
2024-07-19 00:30:32 -07:00
2024-07-28 21:34:14 -07:00
2024-07-19 00:30:32 -07:00
2024-04-15 15:24:30 -07:00
2024-07-19 00:30:32 -07:00
2024-03-19 11:45:09 -07:00
2024-07-09 14:25:42 -07:00
2024-07-23 11:43:12 -07:00
2024-07-09 14:25:42 -07:00
2024-07-25 18:52:20 -07:00
2024-07-19 00:30:32 -07:00
2024-06-17 16:12:19 -04:00