public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/60782] DWARF does not represent _Atomic
Date: Mon, 08 Dec 2014 22:33:00 -0000	[thread overview]
Message-ID: <bug-60782-4-KL8j3dUMxk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60782-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60782

--- Comment #3 from Mark Wielaard <mark at gcc dot gnu.org> ---
Author: mark
Date: Mon Dec  8 22:32:23 2014
New Revision: 218496

URL: https://gcc.gnu.org/viewcvs?rev=218496&root=gcc&view=rev
Log:
DWARFv5 Emit DW_TAG_atomic_type for C11 _Atomic.

This implements the DW_TAG_atomic_type for C11 _Atomic proposal as adopted
in the latest DWARF5 draft. http://dwarfstd.org/ShowIssue.php?issue=131112.1

gcc/ChangeLog

    PR debug/60782
    * dwarf2out.c (modified_type_die): Handle TYPE_QUAL_ATOMIC.

gcc/testsuite/ChangeLog

    PR debug/60782
    * gcc.dg/debug/dwarf2/atomic.c: New test.
    * gcc.dg/debug/dwarf2/stacked-qualified-types-3.c: Likewise.

include/ChangeLog

    PR debug/60782
    * dwarf2.def: Add DWARFv5 DW_TAG_atomic_type.

Added:
    trunk/gcc/testsuite/gcc.dg/debug/dwarf2/atomic.c
    trunk/gcc/testsuite/gcc.dg/debug/dwarf2/stacked-qualified-types-3.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/dwarf2out.c
    trunk/gcc/testsuite/ChangeLog
    trunk/include/ChangeLog
    trunk/include/dwarf2.def


      parent reply	other threads:[~2014-12-08 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 20:18 [Bug debug/60782] New: " tromey at gcc dot gnu.org
2014-06-23 17:08 ` [Bug debug/60782] " mark at gcc dot gnu.org
2014-09-22  9:11 ` mpolacek at gcc dot gnu.org
2014-12-08 22:33 ` mark at gcc dot gnu.org [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=bug-60782-4-KL8j3dUMxk@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).