From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Differentiate empty vs. opaque types
Date: Tue, 10 Apr 2007 21:19:00 -0000 [thread overview]
Message-ID: <20070410211902.GF2056@caradoc.them.org> (raw)
In-Reply-To: <20070312213611.GA6633@host0.dyn.jankratochvil.net>
On Mon, Mar 12, 2007 at 10:36:12PM +0100, Jan Kratochvil wrote:
> 2007-03-12 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdbtypes.h (TYPE_FLAG_STUB_SUPPORTED, TYPE_STUB_SUPPORTED): New
> macros.
> (TYPE_IS_OPAQUE): Empty vs. opaque structures are now
> distinct on the TYPE_STUB_SUPPORTED debug targets.
> * dwarf2read.c (read_structure_type): Set TYPE_FLAG_STUB_SUPPORTED.
> * dwarfread.c (struct_type): New comment on TYPE_FLAG_STUB_SUPPORTED.
>
> 2007-03-12 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.base/type-opaque-lib.c, gdb.base/type-opaque-main.c,
> gdb.base/type-opaque.exp: New files.
Sorry I didn't get back to you; I wanted to finish deleting
dwarfread.c first.
This is OK, without the bit for dwarfread.c, which is now gone.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-04-10 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 22:55 Jan Kratochvil
2007-03-12 3:35 ` Daniel Jacobowitz
2007-03-12 21:36 ` Jan Kratochvil
2007-04-10 21:19 ` Daniel Jacobowitz [this message]
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=20070410211902.GF2056@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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