This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: dbxout.c stabs output problem
- To: Henry Sobotka <sobotka at axess dot com>
- Subject: Re: dbxout.c stabs output problem
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 08 Jul 1998 23:16:57 -0600
- cc: egcs-bugs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <35A1B6FB.6797@axess.com>you write:
>
> 1) Arrays show up as ar0 instead of ar1. The integer represents the
> index type. At first I thought this may be due to some change in stab
> rules, but this weekend I got my hands on dbxout.c and the comments
> starting at line 1293 made it clear that dbxout.c is supposed to be
> putting out ar1 (not to mention that there is no t0, int is t1). For
> example, the egcs dbxout.c produces:
>
> .stabs "STR8:t83=84=ar0;0;7;50",128,0,235,0
> .stabs "STR16:t87=88=ar0;0;15;50",128,0,238,0
> .stabs "STR32:t91=92=ar0;0;31;50",128,0,240,0
> .stabs "STR64:t95=96=ar0;0;63;50",128,0,242,0
>
> compared to gcc 2.7.2's:
>
> .stabs "STR8:t45=ar1;0;7;2",128,0,235,0
> .stabs "STR16:t47=ar1;0;15;2",128,0,238,0
> .stabs "STR32:t49=ar1;0;31;2",128,0,240,0
> .stabs "STR64:t51=ar1;0;63;2",128,0,242,0
Something's definitely wrong, but without a testcase or more info about
what's actually happening in dbxout.c, I can't guess what might be
wrong, whether or not its fixed or anything else.
I think we should nail down this problem first, then look at the second
in more detail instead of trying to deal with both at the same time.
jeff