|
14 February 2014, 18:14
|
#1 |
|
move $dff006,$dff180
Join Date: Feb 2014
Location: USA
Posts: 66
|
vasm question
So I used this well known mini code to test vasm:
Code:
ohai: move $dff006,$dff180
btst #6,$bfe001
bne.s ohai
rts
|
|
|
14 February 2014, 18:17
|
#2 |
|
Registered User
Join Date: Aug 2004
Location:
Posts: 3,333
|
Maybe vlink is putting an empty data hunk in the executable for some reason? Post a hex dump of both versions here. Type test OPT H
|
|
|
14 February 2014, 18:34
|
#3 |
|
move $dff006,$dff180
Join Date: Feb 2014
Location: USA
Posts: 66
|
indeed there is some null data. but that is the version without the linker, which is larger.
|
|
|
|
14 February 2014, 18:46
|
#4 |
|
move $dff006,$dff180
Join Date: Feb 2014
Location: USA
Posts: 66
|
ah no. i was blind. it adds the label...
ReSource: Code:
without linker: ORI.B #????$F3,D0 ORI.B #0,D0 ORI.B #1,D0 ORI.B #0,D0 ORI.B #0,D0 ORI.B #6,D0 ORI.B #????$E9,D0 ORI.B #6,D0 MOVE.W ($DFF006),($DFF180) BTST #6,($BFE001) BNE.B START+$20 RTS ORI.B #0,D0 BSET D1,(A0,D0.W) ORI.B #????$68,D1 BSR.B ???? ORI.B #0,D0 ORI.B #0,D0 ORI.B #????$F2,D0 end with linker: ORI.B #????$F3,D0 ORI.B #0,D0 ORI.B #1,D0 ORI.B #0,D0 ORI.B #0,D0 ORI.B #6,D0 ORI.B #????$E9,D0 ORI.B #6,D0 MOVE.W ($DFF006),($DFF180) BTST #6,($BFE001) BNE.B START+$20 RTS ORI.B #0,D0 db 3 db $F2 end Last edited by marduk_kurios; 14 February 2014 at 19:09. |
|
|
|
14 February 2014, 19:52
|
#5 |
|
Join Date: Jul 2008
Location: Sweden
Posts: 2,269
|
Specify -nosym to remove unnecessary symbol information.
|
|
|
|
14 February 2014, 19:57
|
#6 |
|
move $dff006,$dff180
Join Date: Feb 2014
Location: USA
Posts: 66
|
Ah! Indeed, now it's 60 bytes as well.
In the make script there is no -nosym option though, i assume the linker removes it? |
|
|
|
14 February 2014, 20:03
|
#7 |
|
Join Date: Jul 2008
Location: Sweden
Posts: 2,269
|
Yes, the -s option strips away all symbols.
|
|
|
|
14 February 2014, 20:06
|
#8 |
|
move $dff006,$dff180
Join Date: Feb 2014
Location: USA
Posts: 66
|
Thank you. I should have been able to figure this out myself actually. Hexdumping and checking all options in the documentation sure is not that hard. However, played around with so many assemblers in the recent days that i'm sometimes confused.
|
|
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Latest Win32 VASM Build? | bodhi | Coders. Asm / Hardware | 89 | 25 August 2017 01:27 |
| vasm and word alignment | Den | Coders. Asm / Hardware | 9 | 07 February 2014 11:25 |
| vasm dead code removal | dalton | Coders. Asm / Hardware | 17 | 01 October 2013 14:31 |
| vasm fsincos | dalton | Coders. Asm / Hardware | 4 | 03 September 2012 10:35 |
| vasm 1.5 RFC | phx | Coders. General | 30 | 11 December 2010 02:08 |
|
|
