A.D.A. Amiga Demoscene Archive

Here is the screenshot of that problem I had at the top of the thread.

http://www.pvv.org/~espenamo/asmone_strangebehavio ur.png

Try to increase workspace mem upon startup of ASM-PRO ;)

Or decrease it. :) "Workspace memory full" sometimes means "I couldn't allocate extra memory because I allocated too much workspace memory"

But if I put all code in sections something_f, it works. The section is many megabytes in size though. I haven't tried increasing workmem beyond some 500K or so. I thought the workspace was for the text buffer..

Anyways.. The reasons I switched to AsmPro over Phxass are
- the sine generator
- the AUTO feature!!!
- PRINTT and PRINTV
- the debugger
- that integrated environment feeling. Everything is nearby.

I run in phxass from time to time just to check that asmpro isn't playing some tricks in the same way as Bonkers experienced.

For demos I use phxass though. Object files'n'shit knowamsayn..

All your code, data and bss sections have to fit in the workspace, along with the source code and some of Asm-Pro's internal stuff like symbol tables etc. Asm-Pro does require a bit of memory available besides the workspace (and of course so does the OS and other processes.

Bonkers: I have experienced that a few times as well - the thing not working outside AsmPro. Most often it is some uninitialized register. Best first try is usually to set all registers (except a7) to 0 at the very start of the code and see if the difference is still there.

All your code, data and bss sections have to fit in the workspace, along with the source code and some of Asm-Pro's internal stuff like symbol tables etc. Asm-Pro does require a bit of memory available besides the workspace (and of course so does the OS and other processes.


This doesn't explain that this bug doesn't occur when the section is forced into fastmem with _F even if section is bigger than the allocated workspace. I often experienced this bug too (and, it is a major bug because if you are lucky, it just gives these "workspace memory full" errors until you press ctrl+c. If you are not lucky however you might face a reboot and this is anything but funny. ;)

Idunno, I always use _f anyway. Don't want my stuff running from chip memory under any circumstances. Makes me look bad. :)

doom: 10 years ago a friend of mine made a small program that patched
alocmem. So your fastmem sections can be run on a chip only amiga.

http://aminet.net/package/util/boot/AnyMEM_v14

Nooo!!

Speaking of small programs...

I have long thought about making a small "AsmPro break" utility to break AsmPro out of an infinite loop using a hotkey. Since AsmPro traps all illegal instructions and such itself, it should only be a matter of pointing the program pointer of the AsmPro process to an illegal instruction. Could be really useful, also to interrupt one's own code running inside AsmPro.

Blueberry: That's what Level7 buttons are for. ;D But cool idea, would be a useful addition to AsmPro. Not sure if it's easy to do though. But good luck if you should ever start implementing that. :)

rload: What do PRINTT and PRINTV do in AsmPro? Are they output macros or something?

PRINTT "some text string"

prints text when assembling

value set 5

or

value equ 5

PRINTV value

prints 5 when assembling.

You can use also use printv to display how many bytes a piece of code is.

label:
move.l d0,d0
move.l d0,d0
move.l d0,d0
move.l d0,d0
move.l d0,d0
end:
printt "Innerloop:
printv end-label

when assembling the compiler will output:

innerloop: 10

ah, cheers. That's handy to know. :)

Slightly OT: Is there a predefined symbol (e.g. __asmone, __devpac,..) implemented in DevPak, AsmOne, OMA, etc., so that assembler specific compilation directives are possible?

Slightly OT: Is there a predefined symbol (e.g. __asmone, __devpac,..) implemented in DevPak, AsmOne, OMA, etc., so that assembler specific compilation directives are possible?

Asm1/Pro don't have a predefined symbol. Dunno about the others but I think at least PhxAss doesn't have something like this either. However, it can easily be "emulated" with a define. In my 3d engine I have this f.e.



That way you can dis-/enable Assembler specific things.

another one. If you see something like this, then it is probably an unknown symbol used in a macro.

Of course it's an unknown symbol in a macro. Because that would be an error. And it tells you that an error occurred. Duh!

The sharp way to handle this is to assemble and as soon as it starts spewing out text. Just press ctrl+c to see what the actual error is as it is at the top of the log...

hurray!

Hi Coderz,

I tracked the problem down to a minimum:


Result:

--

The address of Lab seems to be different in Pass 1 and Pass 2. This could only be if AsmPro assumes SYMBOL as defined in Pass 1 and not defined (as it should be) in Pass 2. But most likely there's a bug in the implementation of IFND because the reverse test with IFD works properly in AsmPro. I'd like to use IFND to prevent multiple includes. Is there an other way to do this?

Regards,
dOc.K

Just Crashing In :-)

I was acutually looking for the AsmPro pages to see if there was a newer version, but surf.to/asmpro doesn't work anymore. If anyone has a new address, then please. Then I can update my link page.

About the 'Code moved during pass 2' errors: The way ASM-One works code should be at the same place in both runs. If (by using macro's or IF statements) some code is no longer available in one of the two passes, you will get this error.

I've tried to go around this in ASM-One, but to fix it I would have the rewrite the assembler part from scratch.

I also read that there was a complain that ASM-One does only support 8x8 characters. That is true, and even though I didn't know that AsmPro did support that, I worked on adding other font sizes (as long as they are fixed) about a year ago. It all seemed to work fine than. But when I lately started working on it again it was quite a mess. ASM-One should be able to work with different font sizes in RTG mode and there is a good change I'll will give it another change in the future.

And ASM-One does also support Highlighted errors, but only for immediate operands at the moment. But unlike AsmPro it will Highlight the part that is the problem instead of the part after the problem.

Well, I know, I shouldn't promote ASM-One in a AsmPro thread, but while I'm at it, ASM-One:

- is faster in RTG than AsmPro, and you can disable RTG on non RTG Amiga's. However, it doesn't use a much colors
- supports reading to and writing from the Clipboard
- supports sources bigger than 65535 lines
- supports all the MC68k upcodes and addressing modes
- supports PPC assembly/disassmbly (experimental though)

Besides, there are always bugs that needs to be fixed. And even though I have no problem assembling ASM-One within ASM-One, that unfortunaly doesn't automatically mean that your source will (specialy not if you have used another assembler).

However, if you want to give it a try: http://www.theflamearroes.info is the place. Or at least download it and read the AmigaGuide provided with it. A lot of it is also true for AsmPro.

And for the record: AsmPro is based on the unreleased v1.28 version of ASM-One. Even if you would take the time to add the labels from the original ASM-One to AsmPro, you still would have about 50% of unknown labels, which would still make it pretty unreadable. That is why I admire the work Solo did (and other coders who updated AsmPro). I also liked it because it gave me some competition (AsmPro is the only reason I added RTG support to ASM-One). I truely hope people will continue to work on AsmPro and keep it alive...

Greetz,

Boushh of TFA

P.S. I'll upload a new version this weekend because ASM-One didn't work anymore on MC68000 and/or Kickstart 2.x based systems.

Aha found it:

http://members.home.nl/m.reestman/asmpro.html

encountered the "code moved during pass 2" problem today, but in asm-one, when I tried to implement protection against including the same source twice.. here goes the code:

ifnd matlib

matlib set 1

... code here ...

endc

I guess it must be that the matlib symbol isn't set in pass 1 so the code is included. But then in pass 2 it's set so the code isn't included. Is there any workaround?


(how can I post code here that looks like code? fixed-width chars..)

I think the tag used to be called "pre", but the code blocks had a limited width of 40 characers with preset tabs and usually came out wrong anyway.

Did you try using a symbolic name instead of a variable? i.e matlib = 1 instead. This could be a problem you can only solve by putting the code in a different module and using a separate assembler and linker.

nopes matlib=1 doesn't work either... there's probably no difference between '=' and 'set'

Maybe you can do like this

ifnd matlib
matlib set 1
else
matlib set matlib+1
endc

And the check if matlib == 1 || matlib == 3 then include, strange workaround but might work...

yes thats a bit odd, but it should work =)

I use a ONCE macro which looks like this (how is it I do this fixed-width text again?):

ifnd ONCE
ONCE macro
ifnd \1_FLAG
\1_FLAG set 1
\1\@ set 1
FLAG set 1
else
ifd \1\@
FLAG set 1
else
FLAG set 0
endc
endc
if FLAG
endm
endc

As you can see, the ONCE-macro itself is guarded so it will not be defined more than once even if I include the definition everywhere.

I can then write

ONCE Somename
; things here
endc

with a different name for each ONCEd block.

I'll admit that Todi's method is somewhat simpler. :)