| |
Slammer
Registered: Feb 2004
Posts: 416 |
Kick Assembler Thread 2
The previous thread took a little long to load, so this is a new fresh one.. |
|
... 592 posts hidden. Click here to view all posts....
|
| |
Slammer
Registered: Feb 2004
Posts: 416 |
The site can't be updated right now, so I uploaded the new release to CSDB.
** It also seems that my email is dead, so pm me here on CSDB instead (The feedback on the site, and the kickass@theweb.dk address won't work) **
Nitro: I fixed the dir bug, however because of the filesize of the executable I can't upload it to csdb. About execution times, I noticed that it takes some time to load the first time you run KickAss.exe, but then it gets faster (probably some libraries have to be loaded or something). Have you tried to time it with the -time option? If the performance seems much worse let me know. |
| |
Nitro
Account closed
Registered: Aug 2008
Posts: 13 |
I wasn't talking about the executable load time but assemble time, the differences are huge :)
EXE: Assemble time = 9168 ms
JAR: Assemble time = 2010 ms
I'm including about 33 files, 4,85kb each. |
| |
Mace
Registered: May 2002
Posts: 1799 |
Haha, and then ppl say JAVA is slow! |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Ok, I wasn't aware of this. I can only recomend using the java version then. I might tweak the compiler to produce faster code, but my hopes are not high (Perhaps they forgot to buffer the input in the load library) |
| |
Mace
Registered: May 2002
Posts: 1799 |
Copied from "What assembler/compiler are you using?"
Quoting SlammerWhats your favorite feature of the assembler you are using? What feature really helps you? (...)
The main reason why I switched from 64TASS to KickAss is because of the List() directive, math functions like sin() so I don't need a sinus generator anymore.
Namespacing and scoping look useful too, but have had no need for them yet.
What I like less about KickAss compared to 64TASS is the import of binaries. In 64TASS it's a matter of .binary "file",offset,length and it's in the memory.
No need to do .fill stuff and such. |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Mace: Have you tried
.import binary Music.bin or
.import c64 "prog.c64"
I'll se if I can add an optional offset and length parameter in a later version. (until then you can always write a macro (.macro importFile(filename,offset, length) {..})
Btw. The favorite feature question is intended for all assemblers. |
| |
Mace
Registered: May 2002
Posts: 1799 |
Of course I tried .import, but it's not the same since it fetches the entire file and not just a part of it.
What I use the offset and length for is for importing parts of externally created data, like graphics. |
| |
Digger
Registered: Mar 2005
Posts: 424 |
Slammer, I am getting a weird error after first pass:
Memory Map
----------
WARNING! No data in memory!
What's that about? I've searched the manual but no info there.
Thanks!
|
| |
Slammer
Registered: Feb 2004
Posts: 416 |
You have assembled a program that contains no bytes. Eg. if you assemble
.for(var i=0; i<10; i++)
.print "i="+i
you will get the 'WARNING! No data in memory!'. The first two lines is the memory map which is empty. |
| |
Iapetus/Algarbi/Wood
Registered: Dec 2004
Posts: 71 |
I am getting a problem when I use //, the compiler can't find lables after the use of //
For instance:
lda #$00
sta pintaTileX+1
pintaTileY: lda #$00 // y coord
.
.
.
pintaTileX: lda #$00
Error: Unknown symbol 'pintaTileX'
If I change the first line containing // to:
pintaTileY: lda #$00 /* y coord */
it works
|
| Previous - 1 | ... | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | ... | 61 - Next |
