Home Original page

treatment of operands to .file/.appfile

Jan Beulich JBeulich@novell.com
Tue Apr 19 15:25:00 GMT 2005 
Nick, Ian,

wrt. the comments regarding file names in PR/847, I collected a pseudo-source file that indicates where (and how) file names would get altered with the current code. I'd like to come to an agreement on how gas should deal with this; as I stated in the PR I think file names should not be altered independent of the target. If that seems undesirable to you, then working around this in ia64 (in order to make it work consistently with the Intel assembler, which is one of my current goals) may require quite intrusive changes elsewhere. I'm not really looking into fixing other architectures at present. If this seems like the right course of action, then I would to convert the below into a set of tests (one for each .file directive, since there seem to be varying opinions whether more than one such directive is valid in a single translation unit, and hence looking forward it might turn out the sequence of them could get rejected).

	# delta (m68k sub-target)
	.file "~tilde"

	# ia64
	.file "hash#"

	# m68k
	.opt nocase
	.file "lower"
	.file "UPPER"

	# mmix
	.file ":colon"
	.prefix prefix
	.file "/dir/file.s"

	# ppc/xcoff
	.file "[brackets]"
	.file "{braces}"

	# thumb (arm sub-target)
	.file "slash/data"

	# xtensa (through --rename-section file.s=file.c)
	.file "file.s"

Jan
More information about the Binutils mailing list