Reference | 1. Interface conventions »

Reference¶

1. Interface conventions
- 1.1. Support policy
- 1.2. Language
- 1.3. Headers
- 1.4. Identifiers
- 1.5. Types
- 1.6. Functions
- 1.7. Type punning
- 1.8. Macros
- 1.9. General types
2. Keyword arguments
3. Error handing
- 3.1. Result codes
- 3.2. Assertions
  - 3.2.1. Assertion handling
  - 3.2.2. Common assertions and their causes
- 3.3. Varieties
4. Arenas
- 4.1. Client arenas
- 4.2. Virtual memory arenas
- 4.3. Arena properties
- 4.4. Arena states
- 4.5. Running garbage collections
- 4.6. Using idle time for collection
- 4.7. Arena introspection and debugging
- 4.8. Arena extension callbacks
5. Pools
- 5.1. Pool classes
- 5.2. Pool introspection
6. Allocation
- 6.1. Manual allocation
- 6.2. Allocation points
- 6.3. Allocation point protocol
- 6.4. Example: allocating a symbol
- 6.5. Cautions
- 6.6. Example: inserting into a doubly linked list
- 6.7. Allocation point implementation
7. Object formats
- 7.1. Interface
- 7.2. In-band headers
- 7.3. Cautions
- 7.4. Format methods
- 7.5. Object format introspection
8. Scanning
- 8.1. Scanning protocol
- 8.2. Tagged references
- 8.3. Critical path
- 8.4. Ambiguous references
- 8.5. Unfixed references
- 8.6. Example: Scheme objects
- 8.7. Scanning interface
- 8.8. Fixing interface
- 8.9. Area scanners
9. Threads
- 9.1. Thread safety
- 9.2. Thread registration
- 9.3. Signal and exception handling issues
- 9.4. Fork safety
- 9.5. Thread interface
10. Roots
- 10.1. Registering roots
- 10.2. Cautions
- 10.3. Thread roots
- 10.4. Ranks
- 10.5. Root modes
- 10.6. Root interface
- 10.7. Root introspection
11. Garbage collection
- 11.1. Generation chains
- 11.2. Scheduling of collections
- 11.3. Garbage collection start messages
- 11.4. Garbage collection messages
12. Messages
- 12.1. Finalization messages
- 12.2. Example: interactive chatter
- 12.3. Message types
- 12.4. Message interface
- 12.5. Message queue interface
13. Finalization
- 13.1. Multiple finalizations
- 13.2. Cautions
- 13.3. Finalization interface
- 13.4. Finalization messages
14. Location dependency
- 14.1. Terminology
- 14.2. Creating dependencies
- 14.3. Adding dependencies
- 14.4. Testing dependencies for staleness
- 14.5. Thread safety
- 14.6. Location dependency interface
15. Segregated allocation caches
- 15.1. Cache interface
- 15.2. Allocation interface
16. Allocation patterns
- 16.1. Ramp allocation
17. Allocation frames
18. Debugging pools
19. Telemetry
- 19.1. Telemetry utilities
- 19.2. Example
- 19.3. Event categories
- 19.4. Environment variables
- 19.5. Decoding the telemetry stream
- 19.6. Making the telemetry stream readable
- 19.7. Loading the telemetry stream into SQLite
- 19.8. Decoding the telemetry stream in Python
- 19.9. Telemetry events
- 19.10. Telemetry interface
- 19.11. Telemetry labels
- 19.12. Customizing the telemetry system
20. Weak references
21. Transforms
- 21.1. Cautions
- 21.2. Interface
22. Plinth
- 22.1. I/O module
- 22.2. Library module
23. Platforms
- 23.1. Platform codes
- 23.2. Platform interface
- 23.3. Historical platform codes
- 23.4. Historical platform list
- 23.5. Platform limitations
24. Porting the MPS
- 24.1. Platform code
- 24.2. Functional modules
- 24.3. Platform detection
- 24.4. Platform configuration
- 24.5. Module selection
- 24.6. Makefile
- 24.7. Porting strategy
- 24.8. Update the documentation
- 24.9. Contribute
25. Deprecated interfaces
- 25.1. Deprecated in version 1.118
- 25.2. Deprecated in version 1.115
- 25.3. Deprecated in version 1.113
- 25.4. Deprecated in version 1.112
26. Security issues
- 26.1. Predictable address space layout on FreeBSD
- 26.2. Address disclosure
- 26.3. Telemetry

Memory Management Reference

Reference¶