From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rn-mailsvcp-ppex-lapp34.apple.com (rn-mailsvcp-ppex-lapp34.apple.com [17.179.253.43]) by mx.groups.io with SMTP id smtpd.web11.1840.1630610680067843252 for ; Thu, 02 Sep 2021 12:24:40 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=rdTxwFWL; spf=pass (domain: apple.com, ip: 17.179.253.43, mailfrom: afish@apple.com) Received: from pps.filterd (rn-mailsvcp-ppex-lapp34.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp34.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 182JCi75028191 for ; Thu, 2 Sep 2021 12:24:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : message-id : date : to; s=20180706; bh=f4oF1ZDYojDadjt7cbdzU1eYHHDIU+4bhH3gTD3unAo=; b=rdTxwFWLYZy59sF3Aa1OvM9s8hwvt6pF4fxbfXN4YIeugv/2QqOKA61kgKy3b09BCqcN SzxwhmdStcDje2rTXxPGld9zdABqFVkpigFMX4JM6JtjYeLYLDUAEcmz7znYH1BauJOY Xs3ZjBZw56m2dskVSOoIOLnQm8uHTWhRwYav6FoPaMR001moeXyqTXsAAkgGKHSQvpEl KjeUMKqaJU9VwLk/pman8ux9Zf9eVOWzbZ2ZGES5wdwVmMHwU3ZzEDep4DhEuZ5q9KCC Rpl0AOF8nBMw3L18NpPwbKJ5Yt2JGk6OAm66WubBLOaVGrUhloCsCI+IKYceANKhnkXD AQ== Received: from rn-mailsvcp-mta-lapp04.rno.apple.com (rn-mailsvcp-mta-lapp04.rno.apple.com [10.225.203.152]) by rn-mailsvcp-ppex-lapp34.rno.apple.com with ESMTP id 3atdy9re05-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 02 Sep 2021 12:24:39 -0700 Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPS id <0QYT011QKN93VDE0@rn-mailsvcp-mta-lapp04.rno.apple.com> for devel@edk2.groups.io; Thu, 02 Sep 2021 12:24:39 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) id <0QYT00R00MMPUM00@rn-mailsvcp-mmp-lapp03.rno.apple.com> for devel@edk2.groups.io; Thu, 02 Sep 2021 12:24:39 -0700 (PDT) X-Va-A: X-Va-T-CD: 5975dd1eaec8696b379f33739df9e0a8 X-Va-E-CD: 19059889972a26404e55ed530ae58a6d X-Va-R-CD: 5b7176e8bf419c2ae4609cc60b3246f0 X-Va-CD: 0 X-Va-ID: 5d02a94b-7a6e-4dac-844f-8b45fb2d2955 X-V-A: X-V-T-CD: 5975dd1eaec8696b379f33739df9e0a8 X-V-E-CD: 19059889972a26404e55ed530ae58a6d X-V-R-CD: 5b7176e8bf419c2ae4609cc60b3246f0 X-V-CD: 0 X-V-ID: d69598d7-76e4-44e1-a423-5c519663fa37 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.790 definitions=2021-09-02_04:2021-09-02,2021-09-02 signatures=0 Received: from [17.235.13.23] (unknown [17.235.13.23]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPSA id <0QYT00J6RN8RM100@rn-mailsvcp-mmp-lapp03.rno.apple.com> for devel@edk2.groups.io; Thu, 02 Sep 2021 12:24:28 -0700 (PDT) From: "Andrew Fish" MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.1\)) Subject: Nasm question? What does @ before a label mean? Message-id: <4DA0CAC7-E488-45A7-A463-EB6B1EF855A4@apple.com> Date: Thu, 02 Sep 2021 12:24:26 -0700 To: edk2-devel-groups-io X-Mailer: Apple Mail (2.3654.20.0.2.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.790 definitions=2021-09-02_04:2021-09-02,2021-09-02 signatures=0 Content-type: multipart/alternative; boundary="Apple-Mail=_30094B91-69AA-40EA-8D8C-5D1B5D28955D" --Apple-Mail=_30094B91-69AA-40EA-8D8C-5D1B5D28955D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 It looks like a label starting with @ is not legal nasm syntax? "Valid characters in labels are letters, numbers, _, $, #, @, ~, ., and = ?. The only characters which may be used as the first character of an = identifier are letters, . (with special meaning: see section 3.9 = ), _ and ?. An = identifier may also be prefixed with a $ to indicate that it is intended = to be read as an identifier and not a reserved word; thus, if some other = module you are linking with defines a symbol called eax, you can refer = to $eax in NASM code to distinguish the symbol from the register. = Maximum length of an identifier is 4095 characters.=E2=80=9D [1]=20 Labels prefixed with @@ are defined as TASM compatible? I ask as I see code [2] that uses @ to start a label? Am I looking at = the wrong version of the nasm documentation, or did I missing something = obvious? [1] https://www.nasm.us/doc/nasmdoc3.html [2] = https://github.com/tianocore/edk2/blob/master/MdePkg/Library/BaseMemoryLib= OptPei/Ia32/CopyMem.nasm#L47 = Thanks, Andrew Fish= --Apple-Mail=_30094B91-69AA-40EA-8D8C-5D1B5D28955D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 It = looks like a label starting with @ is not legal nasm syntax?
"Valid characters in labels are letters, numbers, _, $, #, @, ~, ., and ?. The only characters which = may be used as the first character of an identifier are = letters, . (with special meaning: = see section = 3.9), _ and ?. An identifier may also be prefixed with = a $ to indicate that it is = intended to be read as an identifier and not a reserved word; thus, if = some other module you are linking with defines a symbol = called eax, you can refer to $eax in NASM code = to distinguish the symbol from the register. Maximum length of an = identifier is 4095 characters.=E2=80=9D [1] 

Labels prefixed with @@ are defined as = TASM compatible?

I ask as I = see code [2] that uses @ to start a label? Am I looking at the = wrong version of the nasm documentation, or did I missing something = obvious?


[1] https://www.nasm.us/doc/nasmdoc3.html
[2] https://github.com/tianocore/edk2/blob/master/MdePkg/Library/Ba= seMemoryLibOptPei/Ia32/CopyMem.nasm#L47

Thanks,

Andrew Fish
= --Apple-Mail=_30094B91-69AA-40EA-8D8C-5D1B5D28955D--