This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

Re: ASM_IDENTIFY_LANGUAGE advice


 In message <20000123012341.A96411@dragon.nuxi.com>you write:
  > What is the best handling for "ASM_IDENTIFY_LANGUAGE"?
  > Looking at the various files these are the two formats used.  With a full
  > GNU toolchain is there any reason to be worried about confusing gdb?
  > 
  > alpha/elf.h
  > ~~~~~~~~~~~
  > #define ASM_IDENTIFY_LANGUAGE(FILE)                     \
  >  fprintf(FILE, "\t%s \"GCC (%s) %s\"\n", IDENT_ASM_OP,  \
  >          lang_identify(), version_string)
  > 
  > 
  > mips/osfrose.h
  > ~~~~~~~~~~~~~~
  > /* Identify the front-end which produced this file.  To keep symbol
  >    space down, and not confuse kdb, only do this if the language is
  >    not C.  */
  > 
  > #define ASM_IDENTIFY_LANGUAGE(STREAM)                                   \
  > {                                                                       \
  >   if (strcmp (lang_identify (), "c") != 0)                              \
  >     output_lang_identify (STREAM);                                      \
  > }
I'd tend to lean towards the ELF stuff -- osfrose was used on relatively
obscure systems and probably isn't the cleanest code we've got in the
compiler :-)

Presumably the GNU assembler knows the full syntax of the IDENT directive.


jeff


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