Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • cmucl cmucl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmucl
  • cmuclcmucl
  • Merge requests
  • !21

Fix #40: Move start of heap space higher

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Raymond Toy requested to merge rtoy-fix-40-map-heap-higher into master Aug 29, 2017
  • Overview 0
  • Commits 3
  • Pipelines 0
  • Changes 3

This is a workaround for issue #40 (closed). By moving the start of the heap to a higher address, we can still run on older systems (albeit with reduced max heap size), and run on newer systesm where the C code is now mapped at or overlapping the (old) heap start. Arbitrarily choose 0x60000000 as a compromise.

This also requires moving the foreign linkage start to a different address because the old address overlaps the new C area.

Ideally, we could fix this if we could map the heap wherever the OS wants to put it, but we're not there yet.

Use boot-2017-04.lisp to bootstrap this change from the 2017-04 snapshot.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: rtoy-fix-40-map-heap-higher