From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Keith Seitz <keiths@redhat.com>,
"gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] varobj: call CHECK_TYPEDEF
Date: Fri, 25 Apr 2003 03:47:00 -0000 [thread overview]
Message-ID: <3EA89A2A.4010009@redhat.com> (raw)
In-Reply-To: <20030425002942.GB9492@nevyn.them.org>
> On Thu, Apr 24, 2003 at 03:29:36PM -0700, Keith Seitz wrote:
>
>> On Thu, 2003-04-24 at 15:18, Andrew Cagney wrote:
>
>> > BTW, does ...
>> >
>> > struct t
>> > {
>> > int a;
>> > int b;
>> > };
>> >
>> > typedef struct t T;
>> >
>> > main()
>> > {
>> > static T v = {...};
>> > }
>> >
>> > tickle it?
>
>>
>> Nope, that works properly (except for it being reported as "struct t"
>> instead of "T").
>
>
> [Keith, you had "test for insight/792" in your posted testsuite patch.]
>
> There's at least one compiler bug in this area, where DWARF-2 debug info
> will say struct t instead of T. I fixed it for 3.3 and (I think?)
> 3.2.3. Just in case you start getting confused :)
So, rather than `bug', `probable gcc bug'?
Andrew
next prev parent reply other threads:[~2003-04-25 2:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 20:47 Keith Seitz
2003-04-24 20:52 ` Daniel Jacobowitz
2003-04-24 21:51 ` Keith Seitz
2003-04-24 21:55 ` Daniel Jacobowitz
2003-04-24 22:18 ` Keith Seitz
[not found] ` <3EA84A9B.5020308@redhat.com>
2003-04-24 22:27 ` Keith Seitz
2003-04-24 22:31 ` Andrew Cagney
2003-04-25 0:18 ` Keith Seitz
2003-04-25 2:15 ` Daniel Jacobowitz
2003-04-25 3:47 ` Andrew Cagney [this message]
2003-04-25 5:32 ` Daniel Jacobowitz
2003-06-11 20:07 ` Keith Seitz
2003-06-11 21:01 ` Andrew Cagney
2003-06-11 23:51 ` David Carlton
2003-06-12 0:28 ` Keith Seitz
2003-06-12 1:28 ` Daniel Jacobowitz
2003-06-19 19:28 ` Daniel Jacobowitz
2003-06-19 19:53 ` Daniel Jacobowitz
2003-06-19 20:33 ` Keith Seitz
2003-06-19 20:43 ` Daniel Jacobowitz
2003-06-19 21:30 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EA89A2A.4010009@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox