m68000 | Motorola 68000 interpreter, disassembler and assembler (code emitter) | Interpreter library

Yes, it is supported. I think the problem is your code, which has a couple of errors:

1. To use the goto feature, you need to start the inline assembly statement with the asm goto keywords. You are missing the goto.

2. The label operands are numbered sequentially after the input operands (and of course there cannot be outputs). So failed is operand 4, and therefore you need to refer to it with bcc %l4, not %l0.

With these changes I'm able to compile the code.

By the way, I don't know much about m68k assembly, but it looks like you are clobbering register d1, along with whatever the _BURAM subroutine clobbers, yet those have not been declared as clobbers. Shouldn't you add "d1" and the rest along with "cc"?

Also, it seems like maybe you are expecting the operands d0_fcode, a0_info, etc, to be put in those specific registers, presumably because _BURAM expects them there. Do you have those variables defined register asm to tell the compiler about that, e.g. register int d0_fcode asm("d0");? Otherwise it could for instance choose d4 for the d0_fcode operand. In my test it happens by chance that they get put in the desired registers, without explicitly asking, but that is not safe to rely on.

When you have a type mismatch error, this means that either your input is not defined by what you are trying to find. Since your program was working before, this time you may have accidentally entered a character that you have not defined.

Like negation, NOT, AND, OR, XOR all have their uses.

For one, most of our programming languages, like C, offer these operators, and so these machine code instructions directly implement operators of our programming languages — that's one huge class their uses.

Virtually all processors have these primitive boolean logic operations, and they are useful in perhaps hundreds of thousands of ways.

What C, assembly code, and other languages do with these operators is beyond enumeration.

Hashing, error detection, crypto, bit fields, bit vectors, graphics, machine learning, game engines, software floating point, i/o pin manipulation, etc...

Bit vectors alone are used in probably tens of thousands of algorithms: the various forms of analysis in compiler tech (data flow, others), for one, bloom filters, the list goes on and on.

Here's a way with a packed struct. I compiled it on an x86 with -m32 and got the desired offsets in the disassembly, so I think it should still work for an mc68000: