Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] GCC5/DWARFv5 Handle DW_TAG_atomic_type for C11 _Atomic type qualifier.
Date: Mon, 09 Feb 2015 07:56:00 -0000	[thread overview]
Message-ID: <20150209075601.GG4738@adacore.com> (raw)
In-Reply-To: <1421395212.26117.32.camel@bordewijk.wildebeest.org>

Sorry about the delay in reviewing this.

> > 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.

The part in include is controlled by GCC. As soon as approved there,
it is OK to propagate the change to binutils-gdb.git as well (just
shooting us an email, as if applying an "obvious" patch).

Note that I went to the DWARF website, and verified that this new
tag has been accepted with 0x47 as its value (as proposed here).

Looks good to me, with a couple of slight nits (our faults, I'm afraid,
but fortunately trivially fixed).
> +++ b/gdb/testsuite/gdb.dwarf2/atomic-type.exp
> @@ -0,0 +1,90 @@
> +# Copyright 2014 Free Software Foundation, Inc.

Need to add 2015 to the list (that is: "2014-2015").

> +set asm_file [standard_output_file $srcfile2]
> +#set ptr_size [get_sizeof "void *" 96]

Delete this commented out statement.

> +/* This testcase is part of GDB, the GNU debugger.
> +
> +   Copyright 2004-2014 Free Software Foundation, Inc.

s/2014/2015/.

> +int
> +main()

While at it, would you mind reformatting this as:

main (void)

? There was a decision not too long ago that we'd try to have
the code in our testsuite try to conform to the GCS unless there
was reason not to.


Thank you,
-- 
Joel


  parent reply	other threads:[~2015-02-09  7:56 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
2015-02-04 19:50     ` PING: " Mark Wielaard
2015-02-09  7:56   ` Joel Brobecker [this message]
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=20150209075601.GG4738@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mjw@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