From: Mark Wielaard <mjw@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] GCC5/DWARFv5 Handle DW_TAG_atomic_type for C11 _Atomic type qualifier.
Date: Fri, 23 Jan 2015 16:57:00 -0000 [thread overview]
Message-ID: <1422031106.4858.17.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <1421395212.26117.32.camel@bordewijk.wildebeest.org>
On Fri, 2015-01-16 at 09:00 +0100, Mark Wielaard wrote:
> On Tue, 2014-12-09 at 23:30 +0100, Mark Wielaard wrote:
> > This is a cleanup version of the prototype we discussed 6 months ago.
> > https://sourceware.org/ml/gdb-patches/2014-06/msg00795.html
> > GCC now has support for DW_TAG_atomic_type when using the experimental
> > -gdwarf-5 flag. I fixed up the issues Tom pointed out back in June.
> > And I changed the testcase to use the DWARF assembler.
> >
> > gdb/ChangeLog
> >
> > * c-typeprint.c (cp_type_print_method_args): Handle '_Atomic'.
> > (c_type_print_modifier): Likewise.
> > * dwarf2read.c (read_tag_atomic_type): New function.
> > (read_type_die_1): Handle DW_TAG_atomic_type.
> > * gdbtypes.c (make_atomic_type): New function.
> > (recursive_dump_type): Handle TYPE_ATOMIC.
> > * gdbtypes.h (enum type_flag_values): Renumber.
> > (enum type_instance_flag_value): Add TYPE_INSTANCE_FLAG_ATOMIC.
> > (TYPE_ATOMIC): New macro.
> > (make_atomic_type): Declare.
> >
> > gdb/testsuite/ChangeLog
> >
> > * gdb.dwarf2/atomic.c: New file.
> > * gdb.dwarf2/atomic-type.exp: Likewise.
> >
> > include/ChangeLog
> >
> > * dwarf2.def: Add DW_TAG_atomic_type.
> >
> > OK to commit?
>
> Ping. Rebased version of patch attached.
Ping?
next prev parent reply other threads:[~2015-01-23 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 22:30 Mark Wielaard
2015-01-16 8:00 ` Mark Wielaard
2015-01-23 16:57 ` Mark Wielaard [this message]
2015-02-04 19:50 ` PING: " Mark Wielaard
2015-02-09 7:56 ` Joel Brobecker
2015-02-09 14:20 ` Mark Wielaard
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=1422031106.4858.17.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.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