| |
Krill
Registered: Apr 2002
Posts: 2852 |
Release id #216394 : TSCrunch 1.3
"Thanks to Krill for pushing me to squeeze that one last CPU cycle out of the decruncher and for adding TSCrunch to the list of crunchers supported by the Krill Loader."
My pleasure. :)
Here are some current figures (next loader release soonish):
So TSCrunch is now the first choice when going for performance, and that regardless of CPU load for other tasks concurrent to loading+decrunching. :)
If you need the size, ZX0 is your friend, as it's well-balanced with compression ratio on par with Exomizer 3, but so much faster decompression.
In-place decompression and loader+decruncher fitting at $0200-$0400 go without saying. |
|
... 10 posts hidden. Click here to view all posts....
|
| |
Burglar
Registered: Dec 2004
Posts: 1033 |
Quoting iAN CooG> Of course the binaries differ, but let's not use csdb as git commit history
I don't get what's funny. For the sake of completeness, with "binaries" I meant "The generated crunched prg files", not the executable binaries of the cruncher itself.
In this moment there are 2 tscrunch 1.3 that produce different outputs.
It should be important to increase the version number when a program changes completely its output. I was only suggesting this. That's it. Hopefully it's clearer what I meant. okok :) I still thought it was funny. and I get your point, I keep important dev versions with unique version numbers too and bump after release immediately. |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
I'not sure if I should put this in the goofs section, but on linux the Python and Go versions do behave differently when providing the start address as hex number for the -x option:
tscrunch -x 0x3b53 framework.o framework.prg
It works with Python, but not with Go.
After looking into the code:
Imho you shouldn't parse that param as string just to allow that C64 style of hex numbers starting with $ behaviour.
On linux you can't just use $3b53 without escaping the $ sign anyway and the 0x prefix should work perfectly fine on windows and linux.
An integer should be an integer.
Just my 5 cents.
Anyway: after finally converting my demo framework for usage with tscrunch instead of exomizer I must say, this one is really nice. The -i option is so easy and straight forward and automagically produces files that can directly be fed into the krill loader. Cool! |
| |
Burglar
Registered: Dec 2004
Posts: 1033 |
Quoting spider-j
tscrunch -x 0x3b53 framework.o framework.prg
It works with Python, but not with Go.
After looking into the code:
Imho you shouldn't parse that param as string just to allow that C64 style of hex numbers starting with $ behaviour.
On linux you can't just use $3b53 without escaping the $ sign anyway and the 0x prefix should work perfectly fine on windows and linux.
An integer should be an integer.
Just my 5 cents.
agreed, I hacked it into my fork, so it supports all. but yes, the clean way is indeed using an int and not supporting $xxxx
https://github.com/staD020/TSCrunch/commit/7d8d1ddd3819dd863132.. |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
Quoting Burglaragreed, I hacked it into my fork, so it supports all. but yes, the clean way is indeed using an int and not supporting $xxxx
https://github.com/staD020/TSCrunch/commit/7d8d1ddd3819dd863132..
Cool. Thanks for pointing me to your fork! |
| Previous - 1 | 2 - Next |
