From: Scott Lanning <slanning@theworld.com>
To: kieft_brian@si.com
Cc: linux-assembly@vger.kernel.org
Subject: Re: GAS - \@ in macros and labels
Date: Thu, 30 May 2002 13:13:25 -0400 [thread overview]
Message-ID: <Pine.SGI.4.40.0205301306560.4473325-100000@shell01.TheWorld.com> (raw)
In-Reply-To: <004C6F8A.C21188@si.com>
On Wed, 29 May 2002 kieft_brian@si.com wrote:
> .MACRO tableHdr someArgs
> .SET CMD_NUM,\@
> A_CMD_NUM:
> .DC.W (B_CMD_NUM - A_CMD_NUM)
> stuff....
>
> .ENDM
>
> .MACRO tableEnd someArgs
> B_CMD_NUM:
> .ENDM
>
>
> Unfortunately GAS sees this as literal text and throws a bunch of "symbol
> already defined" errors. Any ideas on how to make the CMD_NUM appear as its
> value in a label? Thanks,
Please tell me if you figure it out. :)
In the meantime, I use `cpp`. Then you can use the concatenation
operator '##', like
#define tableHdr(cmd_num) A_ ## cmd_num:\
and so on..
next prev parent reply other threads:[~2002-05-30 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 14:49 GAS - \@ in macros and labels kieft_brian
2002-05-30 17:13 ` Scott Lanning [this message]
2002-05-30 22:44 ` h-peter recktenwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SGI.4.40.0205301306560.4473325-100000@shell01.TheWorld.com \
--to=slanning@theworld.com \
--cc=kieft_brian@si.com \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox