public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <binutils@sources.redhat.com>
Subject: QUOTES_IN_INSN
Date: Mon, 02 May 2005 08:25:00 -0000	[thread overview]
Message-ID: <s275f1ef.010@emea1-mh.id2.novell.com> (raw)

Currently, only ia64 defines this. In order to facilitate passing strings to macros I think the code protected by this needs to be generally enabled, otherwise stuff like

	.macro m str
	 .asciz "\str"
	.endm

	m "foo;bar"

doesn't work (whereas a plain

	.asciz "foo;bar"

does obviously work).

Are there any contra-indications to such a change (i.e. are there targets that can't tolerate this)?

In any case, shouldn't the code in read.c currently protected by this be dealing with '\n' specially (to at least increment the line counter)? What is the intended meaning of a quoted '\n' anyway? Shouldn't there rather be a warning about a missing closing quote (and the line be terminated there)?

Additionally, as I'm seeing a number of similar issues in the macro handling code: Is there a formal specification somewhere about the expected behavior of both the assembler in general and the macro code in particular, so one could reasonably judge whether a certain construct being rejected or producing unexpected results is a bug

Thanks, Jan

             reply	other threads:[~2005-05-02  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  8:25 Jan Beulich [this message]
2005-05-02 18:50 ` QUOTES_IN_INSN Ian Lance Taylor
2005-05-11  9:13 QUOTES_IN_INSN Jan Beulich
2005-05-11 16:44 ` QUOTES_IN_INSN Hans-Peter Nilsson
2005-05-11 17:32 QUOTES_IN_INSN Jan Beulich
     [not found] <s282446a.086@emea1-mh.id2.novell.com>
2005-05-11 19:05 ` QUOTES_IN_INSN Hans-Peter Nilsson
2005-05-13 13:35 QUOTES_IN_INSN Jan Beulich
2005-05-13 16:20 ` QUOTES_IN_INSN Hans-Peter Nilsson
2005-05-17 13:14 ` QUOTES_IN_INSN Nick Clifton

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=s275f1ef.010@emea1-mh.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=binutils@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).