From: Nick Clifton <nickc@sourceware.org>
To: binutils-cvs@sourceware.org
Subject: [binutils-gdb] Gas Doc: Update example of how .altmacro affects the interpretation of macro arguments.
Date: Tue, 16 Apr 2024 11:07:06 +0000 (GMT) [thread overview]
Message-ID: <20240416110706.726B63858D39@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8c8de179c20bf5225a08599bee21a60fcde898fc
commit 8c8de179c20bf5225a08599bee21a60fcde898fc
Author: Nick Clifton <nickc@redhat.com>
Date: Tue Apr 16 12:06:08 2024 +0100
Gas Doc: Update example of how .altmacro affects the interpretation of macro arguments.
PR 31255
Diff:
---
gas/doc/as.texi | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/gas/doc/as.texi b/gas/doc/as.texi
index 56b5b752b2f..42db11e91da 100644
--- a/gas/doc/as.texi
+++ b/gas/doc/as.texi
@@ -6231,27 +6231,22 @@ specified by position, not keyword. @xref{Altmacro,,@code{.altmacro}}.
Thus for example:
@example
-.altmacro
.macro foo bar=1, baz=2
.print "\bar \baz"
.endm
+foo baz=3
+.altmacro
foo baz=3
@end example
Will print:
-@smallexample
-baz=3 2
-@end smallexample
-
-Rather than the expected:
-
@smallexample
1 3
+baz=3 2
@end smallexample
-
@end table
Note that since each of the @var{macargs} can be an identifier exactly
reply other threads:[~2024-04-16 11:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240416110706.726B63858D39@sourceware.org \
--to=nickc@sourceware.org \
--cc=binutils-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).