public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/63300] 'const volatile' sometimes stripped in debug info
Date: Thu, 25 Sep 2014 07:38:00 -0000 [thread overview]
Message-ID: <bug-63300-4-VaUYeLjw5a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63300-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63300
--- Comment #4 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
Author: krebbel
Date: Thu Sep 25 07:37:36 2014
New Revision: 215582
URL: https://gcc.gnu.org/viewcvs?rev=215582&root=gcc&view=rev
Log:
2014-09-25 Andreas Arnez <arnez@linux.vnet.ibm.com>
PR 63300/debug
* tree.c (check_base_type): New.
(check_qualified_type): Exploit new helper function above.
* tree.h (check_base_type): New prototype.
* dwarf2out.c (get_nearest_type_subqualifiers): New.
(modified_type_die): Fix handling for qualifiers. Qualifiers to
"peel off" are now determined using get_nearest_type_subqualifiers.
2014-09-25 Mark Wielaard <mjw@redhat.com>
PR 63300/debug
* gcc.dg/debug/dwarf2/stacked-qualified-types-1.c: New testcase.
* gcc.dg/debug/dwarf2/stacked-qualified-types-2.c: Likewise.
* gcc.dg/guality/pr63300-const-volatile.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/debug/dwarf2/stacked-qualified-types-1.c
trunk/gcc/testsuite/gcc.dg/debug/dwarf2/stacked-qualified-types-2.c
trunk/gcc/testsuite/gcc.dg/guality/pr63300-const-volatile.c
Modified:
trunk/gcc/dwarf2out.c
trunk/gcc/tree.c
trunk/gcc/tree.h
next prev parent reply other threads:[~2014-09-25 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 16:07 [Bug debug/63300] New: " arnez at linux dot vnet.ibm.com
2014-09-19 17:46 ` [Bug debug/63300] " mark at gcc dot gnu.org
2014-09-22 7:18 ` mark at gcc dot gnu.org
2014-09-25 7:38 ` krebbel at gcc dot gnu.org [this message]
2014-09-26 7:40 ` arnez at linux dot vnet.ibm.com
2014-09-26 7:42 ` arnez at linux dot vnet.ibm.com
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-63300-4-VaUYeLjw5a@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).