Proton Stats Viewer Plug-In

[johngb]

This is a useful little application which works in conjunction with the Proton Library Manager's Pre-Compiler to produce a list of Variables, where and how often they are used and what Ram Bank they sit in.

It probably comes into its own when there are a number of include files and you have grown a big program. It is also helpful to be able to see at a glance where your variables are placed, and as it reports how many times they are used, you can make a judgement on re-arranging your variables to optimise the amount of bank switching.

Important You must have Library Manager installed to use this application.

Hi, its great to see you visiting our forum. Why not try Proton Compiler for FREE? Download the FREE version of Proton Compiler, Its called Amicus18 and its available from HERE Already using proton Compiler??? Get rid of these pesky messages... get LICENSED USER STATUS

Installation is pretty straight forward, simply run the 'exe' file after unzipping. You will also need to install a later version of the Pre-Compiler which I have included in a separate file. (Pre-Compiler goes into Library Tools directory).

Help file is included - I haven't had many takers for beta testing but I have been using it quite a bit myself and am reasonably confident that it OK. Please let me know if you have any problems with it.

To obtain stats you must enable extended stats in the Pre-Compiler set up. You can access the Pre-Compiler set up from the Library Manager.

Enjoy - I hope you find it useful.

[bill9399]

Hi John.

Just downloaded and tested this plugin on a fairly large program.

Seems to be working well here.

One query. Would it be possible to add to the plugin to list variable types also in the stats report?

Regards

Bill

[cgriffin]

... Would it be possible to add to the plugin to list variable types also in the stats report?

Bill, not to take away from John's generosity with his plugins, but there is an easy way to do this... just put an initial at the beginning of every variable indicating what it is, for instance, bVar1 is a byte, fVar2 is a bit flag, wVar3 is a word, dVar4 is a DWord... etc...

I'm sure having your requested feature in the plugin would help ensure consistency, though.

[bill9399]

Bill, not to take away from John's generosity with his plugins, but there is an easy way to do this... just put an initial at the beginning of every variable indicating what it is, for instance, bVar1 is a byte, fVar2 is a bit flag, wVar3 is a word, dVar4 is a DWord... etc...

I'm sure having your requested feature in the plugin would help ensure consistency, though.

Should have thought of using that method, though I have a tendency to name variables in a format which tell me what the variable is intended for, rather than what the variable type is.
Forget the query John. Guess I'm just getting lazier as I get older.

[johngb]

I don't extract the Variable type when I gather stats. The Stats gathering is done by the Pre-Compiler and while it is still reasonably quick I would rather not load it up with any other work.

I only did this originally to be able to provide a warning of unused variables. Since then I have added the usage and bank stats. If you want further analysis I think it would be better to write a separate application which worked directly with the source files and/or the asm file.

I was taking the simplest route by extending the Pre-Compiler as it has to open all the files anyway, however, stats gathering is not the prime purpose for the Pre-Compiler.

[Toley]

Thank you Jonh another very good plugin .

My question is not about the Plugin but about the Bank allocation.

I have a program that use the SD library and it always warned me that a DWord is crossing bank boundaries. I've try to fix it by adding dummy variables with no luck. Now the plugin let me see clearly that all the dummy var I add were placed in another bank!!!

Is there a way to tell the compiler to add a var in a specific bank ?

[johngb]

Normally the library file which gets generated will always be the first file which the Compiler sees unless you choose to specifically call up the library File as an Include in your code. The compiler assigns Variables to RAM in the order it sees them so to add in some additional Vars you need to place them before the var which is crossing the boundary.

This means you need to place the lib file (YourProgName_Lib.pbp) as an include file and dim you dummy vars before the include file.

[Michael_L]

Hi John,
after I've finally managed to install the LibraryManager plus the correct version of the precompiler I compiled and started the Stats view plugin. Unfortunately, it stated in a message box that ' "is not a valid a valid integer value'. I've attached the PSS file (which I had to rename to TXT file). Maybe if you have time you can have look.
Greetings, Michael

[johngb]

I have opened it up in my version and it was fine - just didn't have any Bank info as I don't have your ASM file.

Attached is the program version I run - it ought to be the same as your version but have ago anyway. Also attached is the StatsFormatter file which I used. It should be renamed .fmt.

Hope one of the above sorts it - if it does, if its the statsFormater file which is at fault please send me a copy.

[Michael_L]

No luck. Same error as before.
Michael