- 05 Dec, 2012 1 commit
-
-
Christoph Mallon authored
Infer it from block.
-
- 03 Dec, 2012 1 commit
-
-
Matthias Braun authored
That way the spill engine can rematerialize the loads and needs no extra spills for these values.
-
- 02 Dec, 2012 1 commit
-
-
Christoph Mallon authored
-
- 01 Dec, 2012 1 commit
-
-
Christoph Mallon authored
-
- 28 Nov, 2012 2 commits
-
-
Matthias Braun authored
-
Christoph Mallon authored
The only user knwos, where its sp is.
-
- 27 Nov, 2012 4 commits
-
-
Christoph Mallon authored
-
Christoph Mallon authored
-
Christoph Mallon authored
-
Christoph Mallon authored
-
- 25 Nov, 2012 1 commit
-
-
Christoph Mallon authored
-
- 24 Nov, 2012 1 commit
-
-
Christoph Mallon authored
-
- 13 Nov, 2012 2 commits
-
-
Christoph Mallon authored
-
Christoph Mallon authored
-
- 05 Nov, 2012 1 commit
-
-
Christoph Mallon authored
-
- 29 Oct, 2012 3 commits
-
-
Matthias Braun authored
some inputs had "no requirement" set instead of the correct one
-
Matthias Braun authored
-
Matthias Braun authored
(It was set to NULL in the past to support the STA-architecture, but that backend is not maintained anymore)
-
- 19 Jul, 2012 1 commit
-
-
Christoph Mallon authored
Remove now redundant (and sometimes wrong) location info from the panic messages.
-
- 13 Jul, 2012 1 commit
-
-
Christoph Mallon authored
-
- 28 Jun, 2012 1 commit
-
-
Matthias Braun authored
Get away from the strange set_default_XXX_op style and instead let the code modules register their node ops directly.
-
- 09 Feb, 2012 1 commit
-
-
Matthias Braun authored
-
- 21 Dec, 2011 1 commit
-
-
Matthias Braun authored
-
- 19 Dec, 2011 1 commit
-
-
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().
-
- 09 Dec, 2011 1 commit
-
-
Matthias Braun authored
-
- 07 Dec, 2011 1 commit
-
-
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.
-
- 06 Dec, 2011 1 commit
-
-
Christoph Mallon authored
-
- 05 Dec, 2011 1 commit
-
-
Matthias Braun authored
-
- 10 Nov, 2011 2 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
-
- 17 Aug, 2011 2 commits
-
-
Matthias Braun authored
So we are not forced to use the generic be_Spill, be_Reload functions which don't work correctly with double-width register requirements. This should really fix sparc float spill/reload this time.
-
Matthias Braun authored
-
- 15 Aug, 2011 1 commit
-
-
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)
-
- 21 Jun, 2011 1 commit
-
-
Matthias Braun authored
-
- 01 Jun, 2011 1 commit
-
-
Matthias Braun authored
-
- 27 May, 2011 1 commit
-
-
yb9976 authored
-
- 13 Apr, 2011 1 commit
-
-
Matthias Braun authored
-
- 08 Apr, 2011 2 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
-
- 22 Mar, 2011 1 commit
-
-
Matthias Braun authored
-