This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: recent MIPS mdebug-related changes cause gcc testsuitefailures.
- From: cgd at broadcom dot com
- To: "H . J . Lu" <hjl at lucon dot org>
- Cc: binutils at sources dot redhat dot com,drow at mvista dot com
- Date: 21 Jun 2002 11:33:10 -0700
- Subject: Re: recent MIPS mdebug-related changes cause gcc testsuitefailures.
- References: <yov5lm988php.fsf@broadcom.com><20020621112532.A6964@lucon.org>
At Fri, 21 Jun 2002 11:25:32 -0700, H . J . Lu wrote:
> On Fri, Jun 21, 2002 at 11:18:26AM -0700, cgd@broadcom.com wrote:
> > FYI:
> >
> > It looks like the recent MIPS mdebug-related changes cause gcc testuite
> > (specifically, g++.dg/debug) failures. E.g., see the g++ test .log
> > file output below.
>
> See
>
> http://gcc.gnu.org/ml/gcc-patches/2002-05/msg01601.html
>
> We should add
>
> #undef SDB_DEBUGGING_INFO
>
> for all MIPS_STABS_ELF targets.
hmm. possibly, dunno.
two data points:
* i was using mips-elf which _historically has used mdebug debugging
info. It's OK if that changes, but it's not a target that
historically used MIPS_STABS_ELF. And of course, there _are_ no
"MIPS_STABS_ELF" targets anymore, right, it's all dynamic!
* if one _were_ to want to use -mdebug (since it is dynamic), why
wouldn't -gcoff be OK?
* in order to get the proper effect from gcc, ... it's been a long
time since i looked at the option handling code, but since that msg is
spit out for unrecognized options and those options _are_ recognized
in the specs, wouldn't the specs have to be changed too?
(note that linux's SUBTARGET_ASM_DEBUGGING_SPEC is ... very limited
compared to e.g. the generic one defined in mips.h.)
cgd