File: bad.s

package info (click to toggle)
binutils 2.31.1-11
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 307,644 kB
  • sloc: ansic: 1,161,122; asm: 638,494; cpp: 128,815; exp: 68,557; makefile: 55,816; sh: 22,360; yacc: 14,238; lisp: 13,272; perl: 2,111; ada: 1,681; lex: 1,652; pascal: 1,446; cs: 879; sed: 195; python: 154; xml: 95; awk: 25
file content (37 lines) | stat: -rw-r--r-- 938 bytes parent folder | download | duplicates (23)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
	.text
	.cpu 430x

;;;  Test for the assembler detecting spurious size modifiers.
	
	mov.z	r1, r2
	mov.abc	r1, r2
	mov.bcd	r1, r2
	mov.wcd	r1, r2
	mov.	r1, r2
	bis.a	#8, r2

;;; FIXME: Add more tests of assembler error detection here.

	;;  A NOP is needed *before* an EINT instruction.
	eint
	nop
	;; And *after* a DINT instruction.
	dint
	
	;;  Changing interrupt states in two successive instructions
	;;  might cause an interrupt to be missed.  The assembler
	;;  should warn about this, if the -mz command line option
	;;  is used.
	eint
	dint
	nop		;;  No warning needed here.
	dint
	and	#1, r11 ;; Any instruction will do, not just NOPs.
	clr r2		;; Aliases should trigger the warning too.
	mov #1, r2
	BIC #8, SR
	BIS #8, SR
	MOV.W #1, SR 
	;;  We will also get a warning if the last instruction in the file
	;;  changes the interrupt state, since this file could be linked
	;;  with another that starts with an interrupt change.