|
 On Time RTOS-32 Documentation
 Welcome
 RTTarget-32
RTTarget-32 Programming Manual
 Introduction
Running Win32 Programs without Win32
The i386 Microprocessor
RTLoc: Locating a Program
Running a Program on the Target
Cross Debugging
Using an IDE
The RTTarget-32 API
 RTTarget-32 Native API
RTTarget-32 Header Files
DOS Emulation
DPMI Emulation
Win32 Emulation
Win32 Handles
Win32 Memory Management
Win32 File I/O
Win32 Console I/O
Win32 Date and Time Management
Win32 DLLs
Win32 Exception Handling
Win32 Thread Local Storage (TLS)
Win32 Memory Mapped Files
Win32 API Function Cross Reference
Adding other Win32 Functions
RTTarget-32's Memory Managers
Alternate Heap Manager RTTHeap
Extended RAM Management
ACPI Component Architecture
Demo Programs
Advanced Topics
Compiling and Linking with On Time RTOS-32
Redistributable Components of RTTarget-32
RTLoc Error Messages
RTTarget-32 Reference Manual
RTKernel-32
RTFiles-32
RTIP-32
RTPEG-32
RTUSB-32
|
Win32 Thread Local Storage (TLS)
RTTarget-32 will correctly set up a TLS data segment if one is found in the main application .EXE file or in a statically referenced DLL. Note that only one TLS data segment (either in the .EXE or in one DLL) is supported. In addition, Win32 functions which operate on TLS data are supported (e.g., TlsAlloc, TlsSetValue, Get/SetLastError, etc.). By default, 16 TLS slots are available for applications. The first slot (index 0) is used for the static TLS data segment. The number of available TLS slots can be changed using RTTarget-32 native API function RTSetTlsSlots.
RTTarget-32 does not contain a scheduler for multithreading. However, RTTarget-32's TLS management is fully compatible with RTKernel-32, which can be used to implement separate TLS data and thread variables for each thread.
 Win32 Emulation
 Win32 Exception Handling
 Win32 Memory Mapped Files
|
