Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle volatile array types in dwarf2read.c.
Date: Tue, 01 Jul 2014 20:15:00 -0000	[thread overview]
Message-ID: <1404245713.3766.31.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <87ionhq6mg.fsf@fleche.redhat.com>

On Tue, 2014-07-01 at 12:24 -0600, Tom Tromey wrote:
> This patch is ok.

Thanks, pushed.

> Well, I was thinking this:
> 
>     typedef int atype[23];
>     const atype a;
> 
> However, gcc omits the typedef from the DWARF, so I suppose some
> hand-crafted DWARF would have to be written.

I tried in a couple of ways, but GCC always happily optimizes the
unnecessary typedefs away from the DWARF, so it probably is not an issue
in practice if GDB doesn't completely handle that case.

Cheers,

Mark


      reply	other threads:[~2014-07-01 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 21:35 Mark Wielaard
2014-07-01 16:05 ` Tom Tromey
2014-07-01 18:11   ` Mark Wielaard
2014-07-01 18:25     ` Tom Tromey
2014-07-01 20:15       ` Mark Wielaard [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=1404245713.3766.31.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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