This is the mail archive of the
mailing list for the GCC project.
Re: Add ARM to gas .file/.loc tests
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: Daniel Jacobowitz <drow at mvista dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 23 Nov 2002 21:24:52 -0500 (EST)
- Subject: Re: Add ARM to gas .file/.loc tests
On Sat, 23 Nov 2002, Richard Earnshaw wrote:
> Ok, let me check that I've understood precisely what this 'nop' is for...
> It's only used by configure while trying to test for the presence of .file
> and .loc support in the assembler.
And other similar dwarf2ish features.
> That is, after this point we don't use
> the nop at all (ie we don't start putting extra nops into gcc-compiled
> code as a result of this change).
Correct. But why not check gcc/configure.in:2114 (and further
uses of $insn) for yourself?
> I was initially under the impression that we were generating extra nop
> instructions into the compiled code -- where using the correct nop is
> essential. If this is only for an assembler test, then I see no reason
> why .long shouldn't be used (or maybe .byte 0,0,0,0 if alignment might be
> an issue).
No, alignment is no issue here, it's the first (only) datum in
the file. I've had a patch using ".long 0" in my tree for some