1. 12 Sep, 2016 1 commit
    • Kunshan Wang's avatar
      Clarification. · 39b629ad
      Kunshan Wang authored
      Not changing semantics, but changed the wording to make it clearer.
      
      - Provided an object hierarchy of objects in a Mu IR bundle. This
        describes the "has many" and "refers to" relations between things in a
        bundle.
      
      - Clarify what are "top-level entities". Specifically, "functions" are,
        but "function versions" are not. Stopped using "top-level definitions"
        because "definition" is too text-oriented. The API functions create
        entities.
      
      - Stopped using the term "declaring a function", but use "creating a
        function" and "creating a function version" instead. Now "undefined
        function" and "defined function" simply refers to functions with 0
        versions and functions with 1+ versions, respectively.
      
      - Explicitly state the "function version lookup" when a function is
        executed.
      39b629ad
  2. 30 Aug, 2016 1 commit
    • Kunshan Wang's avatar
      Support for symbols, relocs and primordial threads. · 5fd41775
      Kunshan Wang authored
      - The make_boot_image method is moved to MuCtx because it needs to refer
        to memory locations using handles of IRef types.
      
      - Let global cells be always pinned, and added the get_addr API/CommInst
        to get their addresses.
      5fd41775
  3. 20 Jul, 2016 1 commit
  4. 21 Jun, 2016 1 commit
  5. 13 Nov, 2015 1 commit
    • Kunshan Wang's avatar
      Use frame cursors in stack introspection. · 868f8fd4
      Kunshan Wang authored
      Introduced the framecursorref type. This is to solve performance problem
      when the stack is very deep. The API is still stateless, but a frame
      cursor is mutable. A frame cursor can only be created from a stack in
      the READY<Ts> state, may iterate downwards, and must be explicitly
      closed. Concurrent introspection that races with stack modification (pop
      frames/push frames/resuming a stack) has undefined behaviour.
      
      Also used "resumption point" to simplify the description of stack
      binding. The semantics is not changed. In the concrete syntax,
      resumption points are "beginning of function", "OSR point instruction"
      or "the appropriate place for native function". The Mu cases can be
      mapped to the resumption points in the formal model: entry of the %entry
      block, and the exit of the block where the OSR point instruction is in.
      868f8fd4
  6. 27 Oct, 2015 1 commit
  7. 21 Oct, 2015 2 commits
  8. 09 Oct, 2015 1 commit
  9. 01 Oct, 2015 1 commit
  10. 24 Sep, 2015 2 commits
  11. 14 Sep, 2015 1 commit
  12. 11 Sep, 2015 1 commit
  13. 10 Sep, 2015 1 commit
  14. 31 Aug, 2015 1 commit
  15. 28 Aug, 2015 1 commit
  16. 24 Aug, 2015 1 commit
  17. 22 Jun, 2015 1 commit
  18. 19 Jun, 2015 1 commit
  19. 29 Apr, 2015 1 commit