- 15 Aug, 2011 13 commits
-
-
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)
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
- 12 Aug, 2011 15 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
lpp: call the constraint types lpp_{less|greater}_equal because they are a {less|greater} equal operation
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
yb9976 authored
-
yb9976 authored
-
Andreas Zwinkau authored
-
Andreas Zwinkau authored
This reverts commit a63fa62c. While the inliner could do this right, the fix for now is to not inline such functions.
-
- 11 Aug, 2011 1 commit
-
-
Andreas Zwinkau authored
-
- 10 Aug, 2011 3 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
- 08 Aug, 2011 1 commit
-
-
Matthias Braun authored
Since we have no complicated barrier/prolog stuff in the transform phase anymore we can move away from beabihelper now and create the nodes directly which will be necessary when modeling special constraints like wide aligned registers.
-
- 05 Aug, 2011 4 commits
-
-
Matthias Braun authored
So sparc can handle this case now.
-
Matthias Braun authored
-
Matthias Braun authored
Use a special kind of entity on the frame type instead of a value_type struct inside a method type. This makes replacement of function types slightly easier (it's still a complex operation though) and handling in the backend a bit more consistent since it's more or less a normal stack access (with special offsets).
-
Matthias Braun authored
This was done by removing unnecessary options/options that only allowed marginal tweakings to improve performance while at the same time making the interface cumbersome.
-
- 04 Aug, 2011 3 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-