cosmopolitan/libc/intrin/stack.h

#ifndef COSMOPOLITAN_LIBC_STACK_H_
#define COSMOPOLITAN_LIBC_STACK_H_
#include "libc/thread/thread.h"
COSMOPOLITAN_C_START_

void cosmo_stack_lock(void);
void cosmo_stack_unlock(void);
void cosmo_stack_wipe(void);

bool TellOpenbsdThisIsStackMemory(void *, size_t);
bool FixupCustomStackOnOpenbsd(pthread_attr_t *);

COSMOPOLITAN_C_END_
#endif /* COSMOPOLITAN_LIBC_STACK_H_ */
Make threads faster and more reliable This change doubles the performance of thread spawning. That's thanks to our new stack manager, which allows us to avoid zeroing stacks. It gives us 15µs spawns rather than 30µs spawns on Linux. Also, pthread_exit() is faster now, since it doesn't need to acquire the pthread GIL. On NetBSD, that helps us avoid allocating too many semaphores. Even if that happens we're now able to survive semaphores running out and even memory running out, when allocating *NSYNC waiter objects. I found a lot more rare bugs in the POSIX threads runtime that could cause things to crash, if you've got dozens of threads all spawning and joining dozens of threads. I want cosmo to be world class production worthy for 2025 so happy holidays all 2024-12-18 04:59:02 -08:00			`#ifndef COSMOPOLITAN_LIBC_STACK_H_`
			`#define COSMOPOLITAN_LIBC_STACK_H_`
			`#include "libc/thread/thread.h"`
			`COSMOPOLITAN_C_START_`

			`void cosmo_stack_lock(void);`
			`void cosmo_stack_unlock(void);`
			`void cosmo_stack_wipe(void);`

			`bool TellOpenbsdThisIsStackMemory(void *, size_t);`
Fix ordering of pthread_create(pthread_t *thread) This change fixes a bug where signal_latency_async_test would flake less than 1/1000 of the time. What was happening was pthread_kill(sender_thr) would return EFAULT. This was because pthread_create() was not returning the thread object pointer until after clone() had been called. So it was actually possible for the main thread to stall after calling clone() and during that time the receiver would launch and receive a signal from the sender thread, and then fail when it tried to send a pong. I thought I'd use a barrier at first, in the test, to synchronize thread creation, but I firmly believe that pthread_create() was to blame and now that's fixed 2025-01-03 17:28:39 -08:00			`bool FixupCustomStackOnOpenbsd(pthread_attr_t *);`
Make threads faster and more reliable This change doubles the performance of thread spawning. That's thanks to our new stack manager, which allows us to avoid zeroing stacks. It gives us 15µs spawns rather than 30µs spawns on Linux. Also, pthread_exit() is faster now, since it doesn't need to acquire the pthread GIL. On NetBSD, that helps us avoid allocating too many semaphores. Even if that happens we're now able to survive semaphores running out and even memory running out, when allocating *NSYNC waiter objects. I found a lot more rare bugs in the POSIX threads runtime that could cause things to crash, if you've got dozens of threads all spawning and joining dozens of threads. I want cosmo to be world class production worthy for 2025 so happy holidays all 2024-12-18 04:59:02 -08:00
			`COSMOPOLITAN_C_END_`
			`#endif /* COSMOPOLITAN_LIBC_STACK_H_ */`