From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix PR gdb/11702, printing of static const member variables
Date: Tue, 29 Jun 2010 09:12:00 -0000 [thread overview]
Message-ID: <20100629091207.GA30541@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100628190959.GA16958@host0.dyn.jankratochvil.net>
On Mon, 28 Jun 2010 21:09:59 +0200, Jan Kratochvil wrote:
> (c) I guess the (b) rule works even with current GCC output, no special
> compatibility cludge is needed.
for GDB; GCC should stop emitting DW_AT_declaration for better DWARF
correctness (with no other effect) only for DWARF-4+ as it would break
older=current GDBs otherwise.
No patch or testsuite run tried so far.
Regards,
Jan
next prev parent reply other threads:[~2010-06-29 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 18:25 Doug Evans
2010-06-27 18:35 ` Doug Evans
2010-06-27 18:40 ` Doug Evans
2010-06-27 23:07 ` Doug Evans
2010-06-28 17:06 ` Tom Tromey
2010-06-28 11:02 ` Jan Kratochvil
2010-06-28 18:26 ` Doug Evans
2010-06-28 19:10 ` Jan Kratochvil
2010-06-29 9:12 ` Jan Kratochvil [this message]
2010-06-29 17:07 ` Doug Evans
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=20100629091207.GA30541@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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