-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Preliminary work towards threads on win32
* Implement SB-THREAD * Support WITH-TIMEOUT, etc. Implementation details: * Implement pthreads, futex API on top of Win32. * Adds support for the timer facility using sb-wtimer. * Implement an interruptable `nanosleep' using waitable timers. * Threading on Windows uses safepoints to stop the world. On this platform, either all or none of :SB-THREAD, :SB-SAFEPOINT, :SB-THRUPT, and :SB-WTIMER need to be enabled together. * On this platform, INTERRUPT-THREAD will not run interruptions in a target thread that is executing foreign code, even though the POSIX version of sb-thrupt still allows this (potentially unsafe) form of signalling by default. Does not yet include interruptible I/O, which will be made available separately. Slime users are requested to build SBCL without threads until then. Note that these changes alone are not yet sufficient to make SBCL on Windows an ideal backend. Users looking for a particularly stable or thread-enabled version of SBCL for Windows are still advised to use the well-known Windows branch instead. This is a merge of features developed earlier by Dmitry Kalyanov and Anton Kovalenko.
- Loading branch information
Showing
32 changed files
with
3,275 additions
and
283 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.