1. 02 Jun, 2015 1 commit
  2. 27 Oct, 2014 1 commit
  3. 15 Sep, 2014 1 commit
  4. 21 Aug, 2014 3 commits
  5. 08 Jul, 2014 1 commit
  6. 27 May, 2014 1 commit
  7. 10 Apr, 2014 1 commit
  8. 14 Mar, 2014 1 commit
  9. 14 Feb, 2014 2 commits
  10. 12 Nov, 2013 2 commits
  11. 08 Aug, 2013 2 commits
  12. 04 May, 2013 1 commit
    • Matthias Braun's avatar
      do not include config.h anymore · 0f73b43e
      Matthias Braun authored
      It has been empty for nearly all systems. People who used to put stuff
      in config.h can still create a config.h on their own and inject
      -include (gcc) or /FI (msvc) into their CPPFLAGS.
      0f73b43e
  13. 11 Mar, 2013 1 commit
  14. 05 Jan, 2013 1 commit
  15. 21 Dec, 2012 1 commit
  16. 15 Dec, 2012 1 commit
  17. 12 Dec, 2012 1 commit
  18. 30 Nov, 2012 1 commit
  19. 28 Nov, 2012 4 commits
  20. 26 Nov, 2012 2 commits
  21. 13 Nov, 2012 1 commit
  22. 16 Jul, 2012 1 commit
  23. 13 Jul, 2012 2 commits
  24. 27 Jun, 2012 1 commit
  25. 22 Dec, 2011 1 commit
  26. 10 Nov, 2011 1 commit
  27. 20 Oct, 2011 2 commits
  28. 20 Sep, 2011 1 commit
  29. 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