fwiw, I have found UPX to be a piece of crap for most applications. Their site shows that the idea was conceived and implemented during the days of Pentium I computers, as all their CPU tests show that sort of historical period.
You'd think that would be a good thing, but at the time 16 MB of ram a pretty standard amount to have... which leads me to believe that in order to avoid using RAM for UPX exes, they might have been uncompressed via the filesystem. They boast hardly any memory footprint, so I believe something tricky is being done. Problem is, on computers 10-15x that we have around the office, which have a clock speed of probably 10 to 15 times that, the UPX exe's over a 100mbit network sometimes take WAY longer to load... in the seconds, compared to almost a fingersnap. I'm not sure if my wild guess above is the cause for it, but I tested this on about 5 computers at work to decide to stay away from UPX, despite its nice reduction on our .EXE sizes... I know this probably isn't relevant, but I thought I'd mention it anyhow, in case someone else has noticed this. On Tue, May 18, 2010 at 12:15 PM, Viktor Szakáts <harbour...@syenar.hu>wrote: > Hi All, > > FYI > > upx (even latest) won't work with mingw 4.5.0 built executables, > due to 'CantPackException: TLS callbacks are not supported' error. > > In summary mingw added support for TLS callbacks in > startup code, they also refused to make it optional, > upx chokes on this and upx developer is not familiar > with TLS callbacks, so it wasn't fixed to date. > > Here's the background: > http://old.nabble.com/Re:-TLS-Callback-Support-td27477588.html > http://comments.gmane.org/gmane.comp.gnu.mingw.devel/3550 > > Viktor >
_______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
