1. 05 Dec, 2012 1 commit
  2. 03 Dec, 2012 1 commit
  3. 02 Dec, 2012 1 commit
  4. 01 Dec, 2012 1 commit
  5. 28 Nov, 2012 2 commits
  6. 27 Nov, 2012 4 commits
  7. 25 Nov, 2012 1 commit
  8. 24 Nov, 2012 1 commit
  9. 13 Nov, 2012 2 commits
  10. 05 Nov, 2012 1 commit
  11. 29 Oct, 2012 3 commits
  12. 19 Jul, 2012 1 commit
  13. 13 Jul, 2012 1 commit
  14. 28 Jun, 2012 1 commit
  15. 09 Feb, 2012 1 commit
  16. 21 Dec, 2011 1 commit
  17. 19 Dec, 2011 1 commit
    • Matthias Braun's avatar
      make opcode list global · 6bb28287
      Matthias Braun authored
      The opcode list was a member of irprog before which wasn't really
      handled consistently. Also make sure opcodes are properly freed at
      ir_finish().
      6bb28287
  18. 09 Dec, 2011 1 commit
  19. 07 Dec, 2011 1 commit
    • Matthias Braun's avatar
      correctly implement memop handling · 9fbdcb82
      Matthias Braun authored
      memops are nodes that have memory inputs, you can generically query them
      for their memory input. We can also get rid of get_fragile_op_mem in
      favor of get_memop_mem.
      9fbdcb82
  20. 06 Dec, 2011 1 commit
  21. 05 Dec, 2011 1 commit
  22. 10 Nov, 2011 2 commits
  23. 17 Aug, 2011 2 commits
  24. 15 Aug, 2011 1 commit
    • Matthias Braun's avatar
      big refactoring of arch_XXX functions · 41dc42af
      Matthias Braun authored
      This tries to get the names in a consistent format. We basically have 2
      views on register allocation/constraints now:
      
      1) Register Requirements and Assigments are per-instruction. Each
         instruction has requirements on its inputs and outputs, register get
         assigned for outputs of an instruction (assignment is an attribute of
         an instruction, not of the Proj-nodes).
         The internal datastructures model this form!
      
         The functions here have the form:
           arch_get_irn_register_req_in(node, input_nr)
           arch_get_irn_register_in(node, input_nr)
           arch_get_irn_register_req_out(node, output_nr)
           arch_set_irn_register_out(node, output_nr, register)
      
      2) Register Requirements and Assignments are on firm-values. This view
         allows to query/assign requirements and registers at the Proj nodes
         instead of the repsective predecessors.
         This is a convenience interface modeled on top of the other!
      
         The functions have the form:
           arch_get_irn_register_req(node)
           arch_get_irn_register(node)
           arch_set_irn_register(node, register)
      41dc42af
  25. 21 Jun, 2011 1 commit
  26. 01 Jun, 2011 1 commit
  27. 27 May, 2011 1 commit
  28. 13 Apr, 2011 1 commit
  29. 08 Apr, 2011 2 commits
  30. 22 Mar, 2011 1 commit