| |
Rudi
Account closed
Registered: May 2010
Posts: 125 |
64tass compiler commenting memory?
Hi, just wondering if one can make comments on memory areas when compiling, it would have been much easier to see (get an overview) over stuff in mem after compilation.
To show what i mean, ive drawn red lines where i want to put comments:
so for example an commenting would look like this on the first line:
Memory range: $0801-$0812: Startup code
i dont know if 64tass supports that, but if it does please tell. or atleast it would be an idea for future upgrades. |
|
| |
Count Zero
Registered: Jan 2003
Posts: 1932 |
A quick glance at the 64tass docs doesn't reveal something apparent :(
ACME, Dreamass (and KickAss?) come with quite a few warning options.
e.g. ACME has:
!if * > $a000 {
!warn "Program reached ROM area."
}
Dreamass alike. Maybe Soci has some hidden solution? :) |
| |
soci
Registered: Sep 2003
Posts: 480 |
If you define sections their name will appear as you suggested. Here's an example output (with memory ranges removed) of nested section use:
Section: $1000-$1d9c ext_data
Section: $7000-$7fff ext_data_tmp
Section: $2000-$6fff buffer_data
Section: $0000-$3fff bank0
Section: $4000-$7fff bank1
Section: $8000-$bfff bank2
Section: $c000-$ffff bank3
Section: $0000-$1ffb bank0.bank_8000
Section: $0000-$1af9 bank0.bank_8000.code
Section: $1afa-$1d46 bank0.bank_8000.data
Section: $1e60-$1eff bank0.bank_8000.codeio
Section: $1f00-$1ffb bank0.bank_8000.codeend
Section: $2000-$3fff bank0.bank_a000
Section: $2000-$3a8a bank0.bank_a000.code
Section: $3a8b-$3b05 bank0.bank_a000.data
Section: $3ffa-$3fff bank0.bank_a000.vector
Section: $4000-$5fb4 bank1.bank_8000
Section: $4000-$4ffc bank1.bank_8000.code
Section: $4ffd-$5cab bank1.bank_8000.data
Section: $5e60-$5efc bank1.bank_8000.codeio
Section: $5f00-$5f81 bank1.bank_8000.codeend
Section: $5f82-$5fb4 bank1.bank_8000.codemanj
Section: $6000-$7fff bank1.bank_a000
Section: $6000-$78de bank1.bank_a000.code
Section: $78df-$792f bank1.bank_a000.data
Section: $7ffa-$7fff bank1.bank_a000.vector
Section: $6139-$6148 bank1.bank_a000.code.data2
Section: $8000-$9fb5 bank2.bank_8000
Section: $8000-$9837 bank2.bank_8000.code
Section: $9838-$9a98 bank2.bank_8000.data
Section: $9e60-$9efc bank2.bank_8000.codeio
Section: $9f00-$9f81 bank2.bank_8000.codeend
Section: $9f82-$9fb5 bank2.bank_8000.codemanj
Section: $a000-$bfff bank2.bank_a000
Section: $a000-$ba64 bank2.bank_a000.code
Section: $ba65-$bab4 bank2.bank_a000.data
Section: $bffa-$bfff bank2.bank_a000.vector
Section: $c000-$dfff bank3.bank_8000
Section: $c000-$da1a bank3.bank_8000.code
Section: $da1b-$dd7e bank3.bank_8000.data
Section: $de60-$defc bank3.bank_8000.codeio
Section: $df00-$df81 bank3.bank_8000.codeend
Section: $df82-$dfff bank3.bank_8000.mon_overflow
Section: $e000-$ffff bank3.bank_a000
Section: $e000-$f857 bank3.bank_a000.code
Section: $f858-$f876 bank3.bank_a000.codemon
Section: $f877-$fb76 bank3.bank_a000.data
Section: $fffa-$ffff bank3.bank_a000.vector
Memory areas are anonymous, you can't name them. The assembler merges overlapping ones, concatenates following ones or creates new ones when gaps are used.
It's not simply related to the manipulation of "*", as gaps may be created by ".byte ?" or alignment as well.
You can use ".warn" or ".cerror" similarly to acme for checking assumptions.
.warn "Only ", $1000-*, " bytes left"
.cerror *>$1000, "That was too much by ", *-$1000, " bytes"
|
| |
soci
Registered: Sep 2003
Posts: 480 |
On the other hand I got some ideas how adding comments to memory areas could be implemented. I'll keep this in mind, but no promises. |
| |
Rudi
Account closed
Registered: May 2010
Posts: 125 |
ah. neat. i need to read up on sections. |
