simon@snake.cs.uidaho.edu (Mike Simon) (03/07/91)
I'm looking for anyone with experience using the (unsupported) assembler. It appears to use a non-standard syntax for the M68K machines & I'm stuck just getting entrance and exit conditions set up. Sample code and/or suggestions for further reference would be greatly appreciated. M. Simon Systems Manager Computer Science Dept. University of Idaho Moscow, ID simon@ted.cs.uidaho.edu
krowitz@RICHTER.MIT.EDU (David Krowitz) (03/07/91)
Write a short C, Fortran, or Pascal subroutine which has the argument list and calling convention (call-by-value vs. call-by-reference) that you want to use. Then compile the routine with the -exp option to create an expanded compiler listing of the assembly code. This code will *not* be usuable directly with the assembler, but it will show you the proper setup and cleanup methods for getting in and out of the subroutine. -- David Krowitz krowitz@richter.mit.edu (18.83.0.109) krowitz%richter.mit.edu@eddie.mit.edu krowitz%richter.mit.edu@mitvma.bitnet (in order of decreasing preference)
rees@pisa.citi.umich.edu (Jim Rees) (03/08/91)
In article <1991Mar06.201712.23713@groucho>, simon@snake.cs.uidaho.edu (Mike Simon) writes:
I'm looking for anyone with experience using the (unsupported) assembler. It
appears to use a non-standard syntax for the M68K machines...
I thought it used standard Motorola syntax.
When I feel an uncontrollable urge to write assembler code, I use the gnu
assembler.wjw@eba.eb.ele.tue.nl (Willem Jan Withagen) (03/12/91)
In article <5039ac73.1bc5b@pisa.citi.umich.edu> rees@citi.umich.edu (Jim Rees) writes: =>In article <1991Mar06.201712.23713@groucho>, simon@snake.cs.uidaho.edu (Mike Simon) writes: => => I'm looking for anyone with experience using the (unsupported) assembler. It => appears to use a non-standard syntax for the M68K machines... => =>I thought it used standard Motorola syntax. Start remark Not only does it not use the std-moto syntax, it is also very picky with white space and expressions. And it has a few more curiosities: 1) It works(ed) with possition indepedant code layout. This has changed with OS10.X (but that was to late for me). But it shure doesn't make life much easier. 2) Using the floating point is done by appending a floating point 'command-string' after the call to the portable floating point entry. This is surely not very understandable, and it gets even worse because the manual does not even really explain the floating point code. It only gives the opcodes. Note that I did not try to use the onboard FPU directly. End remark =>When I feel an uncontrollable urge to write assembler code, I use the gnu =>assembler. Does this baby have any documentation with it? last time I looked it did not have anything but the C-code. Ciao, Willem Jan Withagen Eindhoven University of Technology DomainName: wjw@eb.ele.tue.nl Digital Systems Group, Room EH 10.10 P.O. 513 Tel: +31-40-473401 5600 MB Eindhoven The Netherlands
rees@pisa.citi.umich.edu (Jim Rees) (03/13/91)
In article <1103@eba.eb.ele.tue.nl>, wjw@eba.eb.ele.tue.nl (Willem Jan Withagen) writes:
This is surely not very understandable, and it gets even worse because
the manual does not even really explain the floating point code.
It only gives the opcodes.
...
=>When I feel an uncontrollable urge to write assembler code, I use the gnu
=>assembler.
Does this baby have any documentation with it? last time I looked it did not
have anything but the C-code.
Manual? Documentation?