emit code spilled outside a single-statement function

[YashasSamaga]

#emit spills the instructions before the function

func()
	#emit NOP
	#emit CONST.pri 321
	#emit NOP
	#emit CONST.pri 123
	return;
	
main () {
	func();
}

produces

CODE 0	; 0
;program exit point
	halt 0

	nop 
	const.pri 141
	nop 
	const.pri 7b
	proc	; func
	; line 6
	; line 6
	break	; 24
	zero.pri
	retn

	proc	; main
	; line 8
	; line 9
	break	; 34
	push.c 0
	call .func
	;$exp
	zero.pri
	retn


STKSIZE 1000

---

__emit (single instruction) spills it after (except for the first one) the function

func()
	__emit NOP;
	__emit CONST.pri 321;
	__emit NOP;
	__emit CONST.pri 123;
	
main () {
	func();
}

produces

CODE 0	; 0
;program exit point
	halt 0

	proc	; func
	; line 2
	; line 2
	break	; c
	nop
	;$exp
	zero.pri
	retn

	const.pri 141
	nop
	const.pri 7b
	proc	; main
	; line 7
	; line 8
	break	; 34
	push.c 0
	call .func
	;$exp
	zero.pri
	retn


STKSIZE 1000

---

__emit {} doesn't even compile

func()
 	__emit {
		nop
		CONST.pri 321
		NOP
		CONST.pri 123
	}

error 055: start of function body without function header

[YashasSamaga]

__emit (single instruction)
__emit ins; is a single statement. Hence, I think an error should've been triggered that the statement is outside the function block.

Interestingly, the following compiles:

__emit nop;

main () {

}

and the nop instruction does end up in the assembly output.

I am not sure if this is supposed to be a bug or a feature. @Daniel-Cortez @VVWVV

---

__emit { }

If for(;;) {} is allowed inside a single-statement function, why shouldn't __emit {} be allowed?

[Daniel-Cortez]

__emit (single instruction) spills it after (except for the first one) the function

func()
  __emit NOP;
  __emit CONST.pri 321;
  __emit NOP;
  __emit CONST.pri 123;
  
main () {
  func();
}

The emit operator works outside of functions just how #emit does. In your example only the 1'st emit statement is treated as if it's inside the function, the others aren't, and that's just how it's supposed to work.

I'll have to look into the emit{} case though.

[Y-Less]

These all seem like errors. So the question of whether they should spill before or after the function is a non-issue. It's neither.

[YashasSamaga]

The compiler source hints that it intentionally allows __emit or #emit outside functions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.