This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

QUOTES_IN_INSN


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]