Ticket #3462 (new task)
New codegen: allocate large objects using allocateLocal()
| Reported by: | simonmar | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.4.1 |
| Component: | Compiler | Version: | 6.11 |
| Keywords: | Cc: | ||
| Operating System: | Unknown/Multiple | Architecture: | Unknown/Multiple |
| Type of failure: | None/Unknown | Difficulty: | Unknown |
| Test Case: | Blocked By: | #4258 | |
| Blocking: | Related Tickets: |
Description
See #3424.
In the new code generator, we should allocate large objects (larger than F * block size, for some suitable fraction F) using the RTS allocateLocal() API rather than from the nursery. It works to allocate them from the nursery -- this is what GHC 6.12 does after the fix in #3424 -- but then they will not be treated as large objects and will be copied during GC. Also, the allocation is likely to fail, requiring a trip through the RTS to put a large enough block in the nursery to satisfy the allocation.
Change History
Note: See
TracTickets for help on using
tickets.
