1. 18 Jul, 2014 2 commits
  2. 10 Apr, 2014 1 commit
  3. 08 Apr, 2014 1 commit
  4. 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
  5. 11 Mar, 2013 1 commit
  6. 29 Jan, 2013 1 commit
  7. 21 Dec, 2012 1 commit
  8. 16 Dec, 2012 1 commit
  9. 15 Dec, 2012 9 commits
  10. 12 Dec, 2012 1 commit
  11. 07 Dec, 2012 1 commit
  12. 25 Nov, 2012 1 commit
  13. 24 Nov, 2012 1 commit
  14. 20 Jul, 2012 1 commit
  15. 13 Jul, 2012 4 commits
  16. 10 Jul, 2012 1 commit
  17. 05 Dec, 2011 1 commit
    • Matthias Braun's avatar
      introduce bedump · 979e11a6
      Matthias Braun authored
      Moves code from ifg dot-file dumpers around and produces .vcg graphs
      now (ycomp layout is way better than xdot)
      979e11a6
  18. 01 Dec, 2011 1 commit
  19. 10 Nov, 2011 1 commit
  20. 20 Oct, 2011 2 commits
  21. 15 Sep, 2011 1 commit
  22. 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
  23. 27 May, 2011 1 commit
  24. 15 Apr, 2011 1 commit
  25. 07 Jan, 2011 1 commit
  26. 27 Dec, 2010 1 commit
  27. 04 Nov, 2010 1 commit