opt. AMOS Pro Compiler Settings?

Cylon · 12 March 2016, 19:20

Hi folks,

i was wondering what might be the best optimal compiler settings for AMOS Pro. I'm asking because i made once an executable with merely 220kB in size, but yesterday it became a whopping 650kB.

Also, the source is swollen up a lot. What is causing this? I am using WinUAE, so there is no speed issue while compiling.

Samurai_Crow · 12 March 2016, 21:40

Are any bank files integrated into the source code?

Cylon · 12 March 2016, 21:54

Quote:

Originally Posted by Samurai_Crow

Are any bank files integrated into the source code?

i don't know!

Will check. I have edited the source a couple dozen times, done some runtime testing and so on. I never included new material, let alone data.

Lonewolf10 · 21 March 2016, 19:45

Did you accidentally include help/error messages in the larger executable?

Did you solve your problem?

It is possible to save compiler settings so that you don't need to keep changing (or remembering them) all the time.

Cylon · 24 March 2016, 13:16

The Problem is: Not always did the source compile. Strange errors or the program wont run. So i have to fiddle around with all the options, that's why it is different all the time.
Will have a look at it tonight, i hope.

Lonewolf10 · 24 March 2016, 17:11

You shouldn't have to fiddle with the settings to get it to compile, unless you want specific features added/removed.

Any chance you could list the errors you get?

I know that AMOS doesn't like lot's of DATA statements - which is why the use of banks is recommended.

Also, are you sure that the compiler is using the same extensions as the editor?

Cylon · 03 April 2016, 00:32

Solved.

below some pics.

The source accumulated lots of data banks during testing - i have no idea why.

The source growed from 160kB to 600 kB.

So i checked with "list bank" what was in there and removed everything with "erase all". I saved the gfx and sound banks first - just to be sure.

Then i compiled again - and it still worked!

Also there was a stupid "out of memory" during my latest tests. The reason was the "SQUEEZE" option in the compiler. Normally this should crunch the executable but now i know it is better not to use it.

Etze · 03 April 2016, 11:33

Quote:

Originally Posted by Cylon

The reason was the "SQUEEZE" option in the compiler. Normally this should crunch the executable but now i know it is better not to use it.

Never worked for me, too. Maybe it only works on a standard-68k-CPU?

Lonewolf10 · 03 April 2016, 20:04

I have never used the SQUEEZE option - I also believe it is known to be buggy (as you have proven).

Cylon · 03 April 2016, 23:08

Quote:

Originally Posted by Lonewolf10

I have never used the SQUEEZE option - I also believe it is known to be buggy (as you have proven).

But when your executable appears to be 650k in size you might think "hell, i'll give it a try!"

Lonewolf10 · 04 April 2016, 22:29

Quote:

Originally Posted by Cylon

But when your executable appears to be 650k in size you might think "hell, i'll give it a try!"

True...

There are some good compressors out there from demo coders that are freely available.

Personally, I use Shrinkler 4.3 (by Blueberry over on the Amiga Demoscene Archive forum) to compress my assembler programs. There is no reason why it shouldn't work with AMOS compiled programs and the compressed output will auto-decrunch when run

Also, the Shrinkler.zip archive has programs that crunch on multiple formats (Linux, Windows 32/64bit and Amiga), but they all produce Amiga only compatible files. What more can you ask for?

(Obviously compressing files is fastest under Windows/Linux (a few seconds) compared to Amiga (several minutes), but decompressing speed is good in my experience so far)

Cylon · 04 April 2016, 22:47

I mostly go for imploder or powerpacker, they are reliable. Never touch that squeeze again, i swear! ;-)

12 March 2016, 19:20	#1
Cylon Registered User Join Date: Oct 2014 Location: Europe Posts: 475	opt. AMOS Pro Compiler Settings? Hi folks, i was wondering what might be the best optimal compiler settings for AMOS Pro. I'm asking because i made once an executable with merely 220kB in size, but yesterday it became a whopping 650kB. Also, the source is swollen up a lot. What is causing this? I am using WinUAE, so there is no speed issue while compiling.

24 March 2016, 17:11	#6
Lonewolf10 AMOS Extensions Developer Join Date: Jun 2007 Location: near Cambridge, UK Age: 44 Posts: 1,924	You shouldn't have to fiddle with the settings to get it to compile, unless you want specific features added/removed. Any chance you could list the errors you get? I know that AMOS doesn't like lot's of DATA statements - which is why the use of banks is recommended. Also, are you sure that the compiler is using the same extensions as the editor? Last edited by Lonewolf10; 24 March 2016 at 17:14. Reason: accidentally submitted before finished typing!

03 April 2016, 00:32	#7
Cylon Registered User Join Date: Oct 2014 Location: Europe Posts: 475	Solved. below some pics. The source accumulated lots of data banks during testing - i have no idea why. The source growed from 160kB to 600 kB. So i checked with "list bank" what was in there and removed everything with "erase all". I saved the gfx and sound banks first - just to be sure. Then i compiled again - and it still worked! Also there was a stupid "out of memory" during my latest tests. The reason was the "SQUEEZE" option in the compiler. Normally this should crunch the executable but now i know it is better not to use it. Attached Thumbnails Last edited by Cylon; 03 April 2016 at 12:12.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Compression of AMOS Pro compiler's "squash" function?	ant512	Coders. General	5	11 February 2014 08:04
Amos Compiler Difficulties	amigapd	support.Apps	7	07 April 2012 15:52
Problem with AMOS Pro compiler install	amigapd	support.WinUAE	2	16 December 2011 15:59
Request AMOS Compiler manual (Scans)	MadAngus	request.Other	4	12 December 2011 11:15
Amos compiler	nnever2000	request.Apps	3	06 September 2006 19:13

12 March 2016, 21:40	#2
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,200	Are any bank files integrated into the source code?

21 March 2016, 19:45	#4
Lonewolf10 AMOS Extensions Developer Join Date: Jun 2007 Location: near Cambridge, UK Age: 44 Posts: 1,924	Did you accidentally include help/error messages in the larger executable? Did you solve your problem? It is possible to save compiler settings so that you don't need to keep changing (or remembering them) all the time.

24 March 2016, 13:16	#5
Cylon Registered User Join Date: Oct 2014 Location: Europe Posts: 475	The Problem is: Not always did the source compile. Strange errors or the program wont run. So i have to fiddle around with all the options, that's why it is different all the time. Will have a look at it tonight, i hope.

03 April 2016, 20:04	#9
Lonewolf10 AMOS Extensions Developer Join Date: Jun 2007 Location: near Cambridge, UK Age: 44 Posts: 1,924	I have never used the SQUEEZE option - I also believe it is known to be buggy (as you have proven).

04 April 2016, 22:47	#12
Cylon Registered User Join Date: Oct 2014 Location: Europe Posts: 475	I mostly go for imploder or powerpacker, they are reliable. Never touch that squeeze again, i swear! ;-)

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)