1. 02 May, 2016 1 commit
  2. 26 Apr, 2016 1 commit
  3. 25 Apr, 2016 1 commit
  4. 24 Apr, 2016 4 commits
  5. 22 Apr, 2016 2 commits
  6. 04 Apr, 2016 3 commits
    • Matthias Braun's avatar
      ia32, amd64: Introduce common x86_addr_t struct. · d13cb0a6
      Matthias Braun authored
      We only use the immediate and scale yet on ia32.
      d13cb0a6
    • Matthias Braun's avatar
    • Matthias Braun's avatar
      be: Rewrite stack frame handling · b6787e36
      Matthias Braun authored
      This is a bigger rewrite of stack frame handling in the backend:
      
      - Do the stack frame type layout late, after all the spill slots have
        been created. This way we can avoid (and remove) the brittle
        frame_alloc_area().
      - Standardize the meaning of stack entity offsets. After stack frame type
        layout they are relative to the stack pointer position at the beginning
        of the function.  It is all in one type now, no splitting into "arg",
        "between" and "stack_frame" type anymore.
      - Generalize the stack pointer simulation code to work with a single
        callback. Represent stack state as current offset and align_padding
        number. Now that callbacks can access and modify them both we do not
        need custom code in the sparc backend anymore.
      - Remove alignment specification on IncSP, only keep a ignore_align flag
        used for the last IncSP that has to remove all existing sp adjustments
        and may end up on a misaligned SP on ia32/amd64.
      - Align stack by default on ia32+amd64 backends.
      b6787e36
  7. 14 Feb, 2016 1 commit
  8. 20 Sep, 2015 1 commit
  9. 07 Sep, 2015 1 commit
  10. 20 Jul, 2015 1 commit
    • Matthias Braun's avatar
      ia32: Introduce FRAMEOFFSET immediate type · 5796136e
      Matthias Braun authored
      This way we don't need a separate frame_entity field in the attribute
      struct anymore. We can also use the immediate type to determine whether
      we need to assign a fresh stackentity to a node.
      This commit does not change the frame_use field, which is now a
      duplicate way to indicate whether we need to assign a stackentity. This
      currently requires a lot of asserts to ensure the two stay in sync. In
      the future I'd like to use frame_use only for the special case when a
      32bit or 64bit entity needs to be forced.
      5796136e
  11. 19 Jul, 2015 4 commits
  12. 05 Jun, 2015 1 commit
  13. 29 Dec, 2014 2 commits
  14. 19 Nov, 2014 1 commit
  15. 16 Nov, 2014 1 commit
  16. 13 Nov, 2014 1 commit
  17. 02 Oct, 2014 1 commit
  18. 24 Jul, 2014 1 commit
  19. 27 Jan, 2014 1 commit
  20. 23 Dec, 2013 1 commit
  21. 04 Nov, 2013 1 commit
  22. 07 Oct, 2013 1 commit
  23. 12 Dec, 2012 1 commit
  24. 30 Nov, 2012 1 commit
  25. 15 Nov, 2012 1 commit
    • Christoph Mallon's avatar
      x87: Simplify x87 code generation. · 0dd7a06d
      Christoph Mallon authored
      Do not store up to three registers for an instruction.
      Instead only store the explicit register operand and whether the operands are permuted and/or the result is to be placed in the explicit register operand or st0.
      0dd7a06d
  26. 12 Nov, 2012 1 commit
  27. 24 Oct, 2012 1 commit
  28. 21 Dec, 2011 1 commit
  29. 10 Nov, 2011 2 commits