path: root/ir/be/bestack.c
diff options
authorMatthias Braun <>2016-04-04 01:08:06 +0200
committerMatthias Braun <>2016-04-04 01:08:08 +0200
commit09e7542fdd72a63e866b5b83e5d35cfcaa03ed54 (patch)
treedb1778b7eb74bbb6432682a254954b9f5c475db0 /ir/be/bestack.c
parent5f9476423d1de594a3723fb7283594247d2d6244 (diff)
be: Let backends deal with memperm offsets
Only the backends know how memperm are implementd and whether they use sp- or fp-relative addressing. This should fix sparc memperm problems. Long-term I'd like to remove the memperm node and use a callback that creates a sequence of target specific nodes instead (similar to how spills and reloads are created).
Diffstat (limited to 'ir/be/bestack.c')
1 files changed, 0 insertions, 2 deletions
diff --git a/ir/be/bestack.c b/ir/be/bestack.c
index 9c86155..3fd879e 100644
--- a/ir/be/bestack.c
+++ b/ir/be/bestack.c
@@ -72,8 +72,6 @@ static void process_stack_bias(sp_sim_func const sim, ir_node *const block,
sched_foreach(block, node) {
if (be_is_IncSP(node)) {
sim_be_IncSP(node, &state);
- } else if (be_is_MemPerm(node)) {
- be_set_MemPerm_offset(node, state.offset);
} else {
sim(node, &state);