vasm - anonymous labels?

[pants]

Does anyone know a nice way of replicating anonymous labels in vasm (ala MASM/FASM etc)?

Excuse nonsensical example:

     REPT   32
     ....
     cmp.l  d0, d1
     bne    @F
     move.l d2, d1
@@:  sub.l  d3, d1
     beq    @F
     move.l d4, d1
@@:
     ....
     ENDR

Where @F & @B are forward/back to next/previous @@?

Yes, it's a lazy 'convenience', but it is convenient and I am lazy :)

It also solves a problem I haven't been able to figure out with vasm - labels in rept blocks (like above). Currently if I have any rept block with labels I'm having to manually expand them (complete with unique label names). The macro solutions (\@, \@!, \@@ etc) don't work outside macros, afaict - or am I missing something obvious?

TIA folks :)

[Edit: Evil thought - macro expansion /inside/ a rept block may just work. Ew...]

[phx]

Yes, anonymous labels are on my to do list since a long time. But it's not easily implemented into vasm without being too intrusive. I also need it for the gas-compatibilty in the std-syntax module.

Currently you have the following workarounds:

1. (Ugly & dangerous) Do branches relative to the current location symbol '*', e.g.:

        bne.b   *+4

2. (Better) Use the INLINE and EINLINE directives, which create a new local name space. Your example works now:

        REPT    32
        inline
        cmp.l   d0,d1
        bne     .1
        move.l  d2,d1
.1:     sub.l   d3,d1
        beq     .2
        move.l  d4,d1
.2:
        einline
        endr

[pants]

Originally Posted by phx

2. (Better) Use the INLINE and EINLINE directives, which create a new local name space. Your example works now:

        REPT    32
        inline
        cmp.l   d0,d1
        bne     .1
        move.l  d2,d1
.1:     sub.l   d3,d1
        beq     .2
        move.l  d4,d1
.2:
        einline
        endr

Nice! Tested and works on all my rept usecases (local/global never mixed) - many thanks for pointing it out! (couldn't find inline/einline in the docs, but just noticed it was in the release notes).

[phx]

Originally Posted by pants

couldn't find inline/einline in the docs

Should be in the doc since last year. It's in chapter 4.4: mot-syntax directives.