Linux assembly list
 help / color / mirror / Atom feed
From: h-peter recktenwald <lx@lxhp.in-berlin.de>
To: Scott Lanning <slanning@theworld.com>
Cc: kieft_brian@si.com, linux-assembly@vger.kernel.org
Subject: Re: GAS - \@ in macros and labels
Date: Thu, 30 May 2002 22:44:35 +0000	[thread overview]
Message-ID: <20020530224435.2d748db8.lx@lxhp.in-berlin.de> (raw)
In-Reply-To: <Pine.SGI.4.40.0205301306560.4473325-100000@shell01.TheWorld.com>

On Thu, 30 May 2002 13:13:25 -0400
Scott Lanning <slanning@theworld.com> wrote:

> 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,

if you want to generate linked/chained lists, you could use 'local' (numeric) 
labels, the range of which is far beyond the documented max. of 9. examples 
can be found in the linux kernel (arch/i386/lib/checksum.S, macroes SRC, DST) 
or, as aplied in "eForth" (http://www.lxhp.in-berlin.de/index-lx.shtml#e4)

regards,
	hp

-- 
Linux,Assembly,Forth: http://www.lxhp.in-berlin.de/index-lx.shtml en/de
NO abusive software patents http://petition.eurolinux.org/pr/pr17.html
-
To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2002-05-30 22:44 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
2002-05-30 22:44   ` h-peter recktenwald [this message]

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=20020530224435.2d748db8.lx@lxhp.in-berlin.de \
    --to=lx@lxhp.in-berlin.de \
    --cc=kieft_brian@si.com \
    --cc=linux-assembly@vger.kernel.org \
    --cc=slanning@theworld.com \
    /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