Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wei-min Pan via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>,
	Weimin Pan via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH,V2 3/5] CTF: handle forward reference type
Date: Wed, 3 Mar 2021 14:01:55 -0800	[thread overview]
Message-ID: <61783d94-0068-305b-cfb5-b776bc29113e@oracle.com> (raw)
In-Reply-To: <87wnuox8s2.fsf@tromey.com>


On 3/3/2021 12:49 PM, Tom Tromey wrote:
>>>>>> ">" == Weimin Pan via Gdb-patches <gdb-patches@sourceware.org> writes:
>>> Added function fetch_tid_type which calls get_tid_type and will set up
>>> the type, associated with a tid, if it is not read in yet. Also implement
>>> function read_forward_type which handles the CTF_K_FORWARD kind.
> Are forward types always filled in?
> Or are they incomplete types (like in C)?

No, these types are not always filled in and can be incomplete.

>
>>> +  TYPE_LENGTH (type) = 0;
>>> +  type->set_is_stub (true);
> I ask because I think you'd only want to do this for incomplete types.
>
> Tom

  reply	other threads:[~2021-03-03 22:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  1:53 [PATCH,V2 0/5] CTF: bug fixes and new features Weimin Pan via Gdb-patches
2021-03-02  1:53 ` [PATCH,V2 1/5] CTF: fix incorrect function return type Weimin Pan via Gdb-patches
2021-03-02  1:53   ` [PATCH,V2 2/5] CTF: set up debug info for function arguments Weimin Pan via Gdb-patches
2021-03-02  1:53     ` [PATCH,V2 3/5] CTF: handle forward reference type Weimin Pan via Gdb-patches
2021-03-02  1:53       ` [PATCH,V2 4/5] CTF: add all members of an enum type to psymtab Weimin Pan via Gdb-patches
2021-03-02  1:53         ` [PATCH,V2 5/5] CTF: multi-CU and archive support Weimin Pan via Gdb-patches
2021-03-02 23:15           ` Lancelot SIX via Gdb-patches
2021-03-03  1:01             ` Wei-min Pan via Gdb-patches
2021-03-03 17:37               ` Lancelot SIX via Gdb-patches
2021-03-03 18:31                 ` Weimin Pan via Gdb-patches
2021-03-03 20:46         ` [PATCH,V2 4/5] CTF: add all members of an enum type to psymtab Tom Tromey
2021-03-03 22:27           ` Wei-min Pan via Gdb-patches
2021-03-03 20:49       ` [PATCH,V2 3/5] CTF: handle forward reference type Tom Tromey
2021-03-03 22:01         ` Wei-min Pan via Gdb-patches [this message]
2021-03-02 12:23     ` [PATCH,V2 2/5] CTF: set up debug info for function arguments Lancelot SIX via Gdb-patches
2021-03-02 18:12       ` Wei-min Pan via Gdb-patches
2021-03-03 20:38       ` Tom Tromey
2021-03-03 21:58         ` Wei-min Pan via Gdb-patches
2021-03-03 20:41     ` Tom Tromey
2021-03-03 20:37   ` [PATCH,V2 1/5] CTF: fix incorrect function return type Tom Tromey
2021-03-03 21:57     ` Wei-min Pan via Gdb-patches

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=61783d94-0068-305b-cfb5-b776bc29113e@oracle.com \
    --to=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    --cc=weimin.pan@oracle.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