Re: GDB PATCH to disable specific G++ demangling

[Eli Zaretskii <eliz at delorie dot com>]

> From: Jason Merrill <jason@redhat.com>
> Date: 15 Dec 2000 14:52:13 +0000
> 
> G++ is in the process of switching to a new ABI, which includes a new
> mangling scheme; therefore, AUTO_DEMANGLING is the best bet for G++ code.
> 
> OK?
> 
> 2000-12-15  Jason Merrill  <jason@redhat.com>
> 
> 	* dbxread.c (read_ofile_symtab): Stay with AUTO_DEMANGLING for G++.
> 	(process_one_symbol): Likewise.
> 	* dwarfread.c (handle_producer): Likewise.
> 
> *** dbxread.c.~1~	Fri Dec 15 14:37:01 2000
> --- dbxread.c	Fri Dec 15 14:39:37 2000
> *************** read_ofile_symtab (struct partial_symtab
> *** 1738,1743 ****
> --- 1738,1746 ----
>         /* Try to select a C++ demangling based on the compilation unit
>            producer. */
>   
> + #if 0
> +       /* For now, stay with AUTO_DEMANGLING for g++ output, as we don't
> + 	 know whether it will use the old style or v3 mangling.  */
>         if (processing_gcc_compilation)
>   	{
>   	  if (AUTO_DEMANGLING)

Could you possibly say a few words about this change, and what exactly
is its effect, for those who don't know by heart what AUTO_DEMANGLING
does?

I recall that I had to make a change in GDB at the time to make it
recognize DJGPP programs as compiled by GCC.  I'd like to make sure
this change doesn't undo what I did back then.  (Unfortunately, I
don't have a recent snapshot on my machine and don't have time to
download and try it, to find this out myself.)

TIA