Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!samsung!think.com!spool.mu.edu!munnari.oz.au!comp.vuw.ac.nz!actrix!tower!johnv From: johnv@tower.actrix.gen.nz (John Veldthuis) Newsgroups: comp.sys.amiga.programmer Subject: Re: Macro-68 Questions Message-ID: <5005.tnews@tower.actrix.gen.nz> Date: 10 May 91 11:36:38 GMT References: <1991May8.205935.26761@unislc.uucp> Organization: Amiga Virus Extermination Services, NZAmigaUG :). Lines: 25 Comment-To: ttobler@unislc.uucp (Trent Tobler) Quoted from <1991May8.205935.26761@unislc.uucp> by ttobler@unislc.uucp (Trent Tobler): > From article , by mykes@amiga0.SF-Bay.ORG (Mike Schwartz): > > >>2) Is bhs.s the same as bhi.s followed by beq.s? That is what > >> I assumed, bhs is not a true 68000 opcode in any case. > >> > > > > bhs.s means "branch higher or same" and it IS a true 68000 opcode. It > > is an unsigned branch while bge is signed. > > No, it is not a true 68000 opcode. The branching instructions are: > [codes deleted] > > These are not anomalies, and you should find these "basic" features in any > > assembler you consider using. They were in the oldest Metacomco assembler > > available... > > So what do the assemblers do? Generate a BHI and BEQ sequence? > no, with Macro68 you can make up Opcodes that are synonyms for other codes. For example if you fancy calling a MOVE instruction PUT then edit the proper file and assemble it and Macro68 will then use PUT the same as MOVE. Real versatile -- *** John Veldthuis, NZAmigaUG. johnv@tower.actrix.gen.nz ***