janbredenbeek wrote:I've done a pull request with my changes, you should be able to merge it into your own source tree.
Much obliged, thank. I'll get that done as soon as I can. Christmas shopping apparently has higher priorities!
janbredenbeek wrote:I've done a pull request with my changes, you should be able to merge it into your own source tree.
NormanDunbar wrote:I'd quite happily create a patch, but at the moment, I cannot find my QMAC assembly/link manual (will be checking with Dilwyn's site later) so that I can assemble and link the two files to test, I've been using GWAS[L] for far too long and never had to use linking. I'm getting too old to remember stuff these days!
NormanDunbar wrote:I have finished (unless you have more correction) the commenting of MON1_ASM now, I think. I've raised a pull request for you to fetch the latest code back into your repository. Github says that it will merge quite happily.
I've also raised three issues (sorry!) as follows:
Enhancement: the V command lists jobs as suspended when they have a non-zero JB_STAT. A -2 is a waiting job (could print a W), -1 is suspended (S) while zero is active. There is also a >0 value which might need to be ignored or handled as well. (I've forgotten what it indicates at the moment!)
Bug?: The F command, to search for hex text never starts searching from the current memory pointer, it always starts at the next address due to the code at the top of the loop incrementing A3 - I think a decrement of A3 is required just before FH_LOOP and just after FH_MEM to fix this.
Bug/Enhancement: The V command shows the total retrieved by MT_FREE but if this is over 60M then it goes negative. I think a test of the top bit of D1.W is required after the divide by 1024, and if set, another divide by 1024 is desired to show MB rather than KB. That should prevent the negatives.
I'd quite happily create a patch, but at the moment, I cannot find my QMAC assembly/link manual (will be checking with Dilwyn's site later) so that I can assemble and link the two files to test, I've been using GWAS[L] for far too long and never had to use linking. I'm getting too old to remember stuff these days!
NormanDunbar wrote:I wonder what else you had running in your 96 Mb set up? MT_FREE returns the biggest area of free ram in the transient memory area I believe (from Pennell) so maybe you had some fragmentation in there perhaps?
For UT_MINT, anything over $7fff is deemed negative so testing just bit 15 should be ok, unless of course someone is running with 32 gb free!
PS. This has been a fun way to while away the hours!
Return to “Software & Programming”
Users browsing this forum: No registered users and 1 guest