Difference between dwarf2out.c and varasm.c

[Manfred Hollstein]

Hi there,

dwarf2out.c and varasm.c disagree in how ASM_BYTE_OP should be defined
if the actual configuration files do not provide a definition.

dwarf2out.c uses:

#ifndef ASM_BYTE_OP
#define ASM_BYTE_OP		".byte"
#endif

while varasm.c uses:

#ifdef ASM_BYTE_OP
	  fprintf (asm_out_file, "%s 0", ASM_BYTE_OP);
#else
	  fprintf (asm_out_file, "\tbyte 0");
#endif

According to gcc.texi varasm.c is right:

`ASM_BYTE_OP'
     A C string constant giving the pseudo-op to use for a sequence of
     single-byte constants.  If this macro is not defined, the default
     is `"byte"'.

I believe, dwarf2out.c should be fixed.

--
 Manfred Hollstein                               Alcatel, Dept. US/EC4
 < mailto:manfred@lts.sel.alcatel.de >             Lorenzstrasse 10
                                                 70435 Stuttgart
 Public PGP key on request                       Germany