Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] gdb: Improve output from "info types" commad
Date: Fri, 19 Jul 2019 19:54:00 -0000	[thread overview]
Message-ID: <0ef0b2d8-ac76-f63d-edd1-b45f8057b48a@redhat.com> (raw)
In-Reply-To: <20190719194331.GB23204@embecosm.com>

On 7/19/19 8:43 PM, Andrew Burgess wrote:
> * Pedro Alves <palves@redhat.com> [2019-07-18 21:07:10 +0100]:
> 
>> On 7/12/19 12:37 PM, Andrew Burgess wrote:

>> I'm not immediately seeing what the C++ testcase is trying to
>> test.  If you replace "class" with struct, and use "typedef struct AA"
>> instead of "typedef AA", isn't that code basically C code as well?
>>
>> Also, might it be a good idea to check the info-types.c stuff in
>> C++ mode as well, to make sure we normalize C and C++ modes?
>> I.e., make gdb.base/info-types.exp compile once as a C program, and
>> once as a C++ program?
> 
> I've removed the gdb.cp/info-types.{cc,exp} files, and extended the
> gdb.base test to include an example of 'class'.

Ah, OK, it's "class" specifically that you were looking at test.
I wasn't sure.

> Yes, we know
> internally they are handled just like structs, but I'd like to cover
> it "just in case".  The gdb.base case is now compiled as C and C++.

Thanks.

Pedro Alves


  reply	other threads:[~2019-07-19 19:54 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 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 [this message]
2019-07-20 13:47       ` 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
2019-07-22 14:10         ` Tom Tromey

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=0ef0b2d8-ac76-f63d-edd1-b45f8057b48a@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