From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gdb: Show type summary for anonymous structures from c_print_typedef
Date: Sat, 20 Jul 2019 13:47:00 -0000 [thread overview]
Message-ID: <1fcef366-f0ca-4503-b5cf-b280120c95cf@redhat.com> (raw)
In-Reply-To: <20190719210636.GD23204@embecosm.com>
On 7/19/19 10:06 PM, Andrew Burgess wrote:
> An additional area of interest is how C++ handles anonymous types used
> within a typedef; enums are handled basically inline with how C
> handles them, but structs (and classes) are slightly different. The
> behaviour before the patch is different, and is unchanged by this
> patch. Consider this code compiled for C++:
>
> typedef struct {
> int i;
> } struct_t;
>
> Both before and after this patch, this is show by 'info types' as:
>
> 3: typedef struct_t struct_t;
Curious, and odd.
> gdb/ChangeLog:
>
> * c-typeprint.c (c_print_typedef): Pass -1 instead of 0 to
> type_print.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.ada/info_auto_lang.exp: Update expected results.
> * gdb.base/info-types.c: Add additional types to check.
> * gdb.base/info-types.exp: Update expected results.
LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-07-20 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 11:37 [PATCH 0/3] Improving "info types" command Andrew Burgess
2019-07-12 11:37 ` [PATCH 1/3] gdb: Switch "info types" over to use the gdb::options framework Andrew Burgess
2019-07-12 12:48 ` Eli Zaretskii
2019-07-19 14:50 ` Andrew Burgess
2019-07-18 20:07 ` Pedro Alves
2019-07-12 11:37 ` [PATCH 3/3] gdb: Show type summary for anonymous structures from c_print_typedef Andrew Burgess
2019-07-19 12:38 ` Pedro Alves
2019-07-19 21:06 ` Andrew Burgess
2019-07-20 13:47 ` Pedro Alves [this message]
2019-07-22 14:10 ` Tom Tromey
2019-07-12 11:37 ` [PATCH 2/3] gdb: Improve output from "info types" commad Andrew Burgess
2019-07-18 20:07 ` Pedro Alves
2019-07-19 19:43 ` Andrew Burgess
2019-07-19 19:54 ` Pedro Alves
2019-07-20 13:47 ` Pedro Alves
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=1fcef366-f0ca-4503-b5cf-b280120c95cf@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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