From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Daniel Jacobowitz <drow@false.org>,
Tom Tromey <tromey@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: RFA: unbreak typedefed bitfield
Date: Mon, 21 Dec 2009 17:37:00 -0000 [thread overview]
Message-ID: <20091221173728.GP2788@adacore.com> (raw)
In-Reply-To: <200912212018.33780.vladimir@codesourcery.com>
> IMO, this usage should just go, in preference to
>
> type_set_length (type, DW_UNSND (attr));
I tend to agree, but maybe for a different reason. I think we should
eventually try to make struct type and main_type opaque, which will
force to get rid of the macros and provide accessors instead.
--
Joel
prev parent reply other threads:[~2009-12-21 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 12:41 Vladimir Prus
2009-12-18 13:06 ` Joel Brobecker
2009-12-18 14:17 ` Daniel Jacobowitz
2009-12-18 14:20 ` Vladimir Prus
2009-12-18 14:24 ` Daniel Jacobowitz
2009-12-21 9:51 ` Vladimir Prus
2009-12-21 13:23 ` Joel Brobecker
2009-12-18 19:55 ` Tom Tromey
2009-12-21 10:00 ` Vladimir Prus
2009-12-21 17:08 ` Tom Tromey
2009-12-21 17:15 ` Daniel Jacobowitz
2009-12-21 17:18 ` Vladimir Prus
2009-12-21 17:37 ` Joel Brobecker [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=20091221173728.GP2788@adacore.com \
--to=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.com \
--cc=vladimir@codesourcery.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