public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Jason Merrill <jason@redhat.com>,
	       Cary Coutant <ccoutant@google.com>,
	       "Joseph S. Myers" <joseph@codesourcery.com>,
	       Joel Brobecker <brobecker@adacore.com>
Subject: Re: Some DWARFv5 proposal prototypes (atomic_type, aligned_type)
Date: Tue, 15 Jul 2014 11:57:00 -0000	[thread overview]
Message-ID: <1405424182.17759.62.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <877g3f3e6f.fsf@fleche.redhat.com>

On Mon, 2014-07-14 at 13:58 -0600, Tom Tromey wrote:
> >>>>> "Mark" == Mark Wielaard <mjw@redhat.com> writes:
> Mark> The following two patches are based on the earlier "dwarf2out.c: Pass
> Mark> one cv_quals argument" and "Emit DW_tag_restrict_type" patches I posted
> Mark> earlier. Since there currently is not even an early draft yet for DWARFv5,
> Mark> just a collection of proposals that might or might not be adopted these
> Mark> patches are not meant to be integrated just yet. But I would like to get
> Mark> feedback on the code and whether the new debug information is useful.
> 
> I didn't read the patches I'm afraid.
> However, the new debug information is definitely useful for the gcc/gdb
> integration project.  Without it I think the user can end up with
> mysterious failures in their compiled expressions.

I don't know how far DWARFv5 is at the moment, these proposals haven't
even made it to a draft yet, so we might have to look at turning them
into GNU extensions first then.

But first I need some feedback on the dwarf2out.c refactoring for
passing around cv-qualifiers and the addition of the restrict tag
patches on which these DWARFv5 prototypes are based:

https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00569.html
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00575.html

Thanks,

Mark

  reply	other threads:[~2014-07-15 11:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 20:56 [PATCH] dwarf2out.c: Pass DWARF type modifiers around as flags argument Mark Wielaard
2014-06-20 11:51 ` Mark Wielaard
2014-06-20 23:02   ` [PATCH] Emit DW_tag_restrict_type for restrict-qualified pointers Mark Wielaard
2014-06-22  9:39     ` [PATCH] DWARFv5 Emit DW_TAG_atomic_type Mark Wielaard
2014-06-23 16:32       ` Tom Tromey
2014-06-23 17:12         ` Mark Wielaard
2014-07-08 16:39     ` [PATCH 1/2] dwarf2out.c: Pass one cv_quals argument instead of two for const and volatile Mark Wielaard
2014-07-09 21:36       ` [PATCH 1/2] DWARFv5 Emit DW_TAG_atomic_type Mark Wielaard
2014-07-09 21:36       ` Some DWARFv5 proposal prototypes (atomic_type, aligned_type) Mark Wielaard
2014-07-14 20:03         ` Tom Tromey
2014-07-15 11:57           ` Mark Wielaard [this message]
2014-07-15 20:55             ` Eric Christopher
2014-07-09 21:37       ` [PATCH 2/2] DWARF5: Add DW_TAG_aligned_type support Mark Wielaard
2014-07-08 16:39     ` [PATCH 2/2] Emit DW_tag_restrict_type for restrict-qualified pointers Mark Wielaard
2014-07-08 18:12       ` Mark Wielaard
2014-07-03  9:53   ` [PATCH] Add guality [p]type test Mark Wielaard
2014-07-03 10:05     ` Jakub Jelinek
2014-07-03 11:15       ` Mark Wielaard
2014-07-03 19:43         ` Tom Tromey
2014-07-07  9:58     ` Richard Biener
2014-08-19 11:06       ` Mark Wielaard
2014-08-19 11:23         ` Richard Biener
2014-08-19 12:10           ` Mark Wielaard
2014-08-19 12:16             ` Richard Biener
2014-08-19 17:52               ` Mark Wielaard
2014-08-20  8:49                 ` Richard Biener
2014-08-20 12:19                   ` Mark Wielaard
2014-08-20 12:31                     ` Richard Biener

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=1405424182.17759.62.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=ccoutant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).