1. 24 May, 2015 1 commit
  2. 25 Dec, 2014 1 commit
  3. 13 Nov, 2014 1 commit
  4. 02 Oct, 2014 2 commits
  5. 15 Sep, 2014 2 commits
  6. 21 Aug, 2014 2 commits
  7. 16 May, 2014 1 commit
  8. 10 Apr, 2014 1 commit
  9. 17 Feb, 2014 1 commit
  10. 28 Oct, 2013 1 commit
    • Matthias Braun's avatar
      remove NEW_ARR_A and use ALLOCAN · fee5ce04
      Matthias Braun authored
      All users of NEW_ARR_A used it to construct a simple array, yet noone
      cared about it actually being an array with a length field in front. For
      this simple use case you should use ALLOCAN.
      fee5ce04
  11. 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
  12. 29 Jan, 2013 1 commit
  13. 12 Dec, 2012 1 commit
  14. 27 Nov, 2012 3 commits
  15. 13 Jul, 2012 1 commit
  16. 06 Jun, 2012 1 commit
  17. 10 Nov, 2011 1 commit
  18. 20 Oct, 2011 1 commit
  19. 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
  20. 21 Jun, 2011 1 commit
  21. 15 Apr, 2011 1 commit
  22. 04 Mar, 2011 3 commits
  23. 04 Nov, 2010 1 commit
  24. 22 Sep, 2010 1 commit
  25. 06 Sep, 2010 1 commit
  26. 02 Jul, 2010 1 commit
  27. 23 Jun, 2010 1 commit
  28. 09 Mar, 2010 1 commit
  29. 17 Sep, 2009 1 commit
  30. 02 Sep, 2009 1 commit
  31. 06 Aug, 2009 1 commit
    • Matthias Braun's avatar
      - Rewrite internal backend logic for querying register constraints. · 0860cafa
      Matthias Braun authored
        (We have a separate get_input, and get_output callback for now).
        This should make the code faster for now and is a first step towards
        changing the interface to query register constraints on the mode_T node
        itself instead of the Proj nodes.
      - Handle middleend node constraints and stuff in benode.c instead of in each
        backend
      - Remove irn_class_branch we already had is_cfop in the middleend
      - Fix a bunch of bugs/problems in the process
      
      [r26320]
      0860cafa
  32. 05 Aug, 2009 1 commit
  33. 24 Oct, 2008 1 commit