e8723be33f
The trap and trapz/trapnz instructions now take a trap code immediate operand which indicates the reason for trapping.
38 lines
1.1 KiB
Plaintext
38 lines
1.1 KiB
Plaintext
; The .cton parser can't preserve the actual entity numbers in the input file
|
|
; since entities are numbered as they are created. For entities declared in the
|
|
; preamble, this is no problem, but for EBB and value references, mapping
|
|
; source numbers to real numbers can be a problem.
|
|
;
|
|
; It is possible to refer to instructions and EBBs that have not yet been
|
|
; defined in the lexical order, so the parser needs to rewrite these references
|
|
; after the fact.
|
|
test cat
|
|
|
|
; Check that defining numbers are rewritten.
|
|
function %defs() {
|
|
ebb100(v20: i32):
|
|
v1000 = iconst.i32x8 5
|
|
v9200 = f64const 0x4.0p0
|
|
trap user4
|
|
}
|
|
; sameln: function %defs() native {
|
|
; nextln: $ebb100($v20: i32):
|
|
; nextln: $v1000 = iconst.i32x8 5
|
|
; nextln: $v9200 = f64const 0x1.0000000000000p2
|
|
; nextln: trap user4
|
|
; nextln: }
|
|
|
|
; Using values.
|
|
function %use_value() {
|
|
ebb100(v20: i32):
|
|
v1000 = iadd_imm v20, 5
|
|
v200 = iadd v20, v1000
|
|
jump ebb100(v1000)
|
|
}
|
|
; sameln: function %use_value() native {
|
|
; nextln: ebb0($v20: i32):
|
|
; nextln: $v1000 = iadd_imm $v20, 5
|
|
; nextln: $v200 = iadd $v20, $v1000
|
|
; nextln: jump ebb0($v1000)
|
|
; nextln: }
|