GitLab

with RegGroup::get_from_value

sequence

normal destination. The call instruction (machine code) has two successors, a normal cont
block which contains the branch to the normal destination, and the exceptional
cont

immiediate number. Richards benchmark runs.

as scale in memory op

res; op res, y -> res. Instead, I used to generate: op x, y -> x; mov x
-> res

(for easy debugging)

stack pointer before calling, unless we pushed arguments by stack)

[wip] let backend know about exception flow. also add one more test to see if callee-saved register is restored
during catching exception, the test failed (and I marked it as ignored).

argument
we need to know whether a block is an exception block by looking at all
the exceptional clauses.

size, etc). add PRINTHEX instruction to print a number (for debugging use)

when proceeding to a new block, prune alive entries based on liveout and
liveins

liveins

a function

This reverts commit 54ce8e1c.

(operand doesnt match instruction, such as movl %rdi, %edx)

block, mark the new block as exceptional block

No regression, but new tests still doesn't run. Marked them
as expect fail or skip. Going to work on them later.