Local labels interfere with naming space

Index > Compiler Internals > Local labels interfere with naming space

Author

Thread

pfranz

Joined: 13 Jan 2007
Posts: 116
Location: Italy

pfranz 22 Nov 2023, 16:35

Local macro labels shouldn't affect naming space, but they do:

Code:

macro m {
local a
a:
}

b:
jmp .c

m

.c:

Here, the local label "hides" .c and this code doesn't assemble.

22 Nov 2023, 16:35

macomics

Joined: 26 Jan 2021
Posts: 928
Location: Russia

macomics 22 Nov 2023, 17:08

Code:

macro m {
local a
a:
}

b:
jmp .c

m

b.c:

Code:

macro global name* {
  if 0
    label name
  end if
}
macro m {
local a
a:
}

b:
jmp .c

m

global b
.c:

22 Nov 2023, 17:08

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 8351
Location: Kraków, Poland

Tomasz Grysztar 22 Nov 2023, 18:28

Section 2.3.3 of the manual wrote:

If the name given as parameter to LOCAL directive begins with a dot or two dots, the unique labels generated by each evaluation of macroinstruction will have the same properties.

Keep in mind that in fasm 1.x architecture preprocessor is a separate stage with its own language, converting entire source before the assembler has a chance to see it (and it is the assembly parser that then interprets properties of labels, like the starting dot). The labels produced in the text of a macro are no different from any other labels during the assembly stage. See the output of PREPSRC tool to get an idea of what text the assembler sees.

If you would prefer an assembler with single, unified language, there is fasmg, fasm's successor. It has proper separation of namespaces and symbols local to macros do not interfere with the other ones.

22 Nov 2023, 18:28

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20300
Location: In your JS exploiting you and your system

revolution 22 Nov 2023, 21:55

Use the double dot.

Code:

macro m {
local ..a
..a:
}

22 Nov 2023, 21:55

pfranz

Joined: 13 Jan 2007
Posts: 116
Location: Italy

pfranz 24 Nov 2023, 02:37

That's what I do, I use one or two dots, but I just found notable that local labels would interfere outside their macros.
Two dots perfectly solve the problem.

24 Nov 2023, 02:37

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20300
Location: In your JS exploiting you and your system

revolution 24 Nov 2023, 02:46

local just creates a unique name, it doesn't make any sort of special label.

Code:

~ cat test.asm 
macro m {
        local a
        display `a,10
}
rept 16 {m}

~ fasm test.asm 
flat assembler  version 1.73.31  (16384 kilobytes memory)
a?0
a?1
a?2
a?3
a?4
a?5
a?6
a?7
a?8
a?9
a?A
a?B
a?C
a?D
a?E
a?F
1 passes, 0 bytes.
~

24 Nov 2023, 02:46

pfranz

Joined: 13 Jan 2007
Posts: 116
Location: Italy

pfranz 24 Nov 2023, 02:53

In my opinion there shouldn't be any special label, it should just be separated from the "outside world" (hence the word "local"). Like this is "semi-local".
Anyway there is no practical problem, another solution is to use:

a = $

instead of

a:

24 Nov 2023, 02:53

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum