From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] DWARF-3+ DW_AT_accessibility defaults #2 (GCC PR debug/45124)
Date: Mon, 21 Mar 2011 20:15:00 -0000 [thread overview]
Message-ID: <20110321201005.GA922@host1.jankratochvil.net> (raw)
In-Reply-To: <m3d3lkv2i0.fsf@fleche.redhat.com>
On Mon, 21 Mar 2011 17:53:43 +0100, Tom Tromey wrote:
> I think this is ok.
Checked in:
http://sourceware.org/ml/gdb-cvs/2011-03/msg00258.html
> I am not really a fan of producer checks, but I couldn't think of
> anything better.
I was curious I haven't found any GCC/G++ DW_AT_producer check so far.
Thanks,
Jan
next prev parent reply other threads:[~2011-03-21 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:47 Jan Kratochvil
2011-03-21 17:29 ` Tom Tromey
2011-03-21 20:15 ` Jan Kratochvil [this message]
2011-03-21 20:41 ` Tom Tromey
2011-03-22 10:06 ` revert+new [patch]: " Jan Kratochvil
2011-03-22 18:16 ` Tom Tromey
2011-03-22 18:32 ` Jan Kratochvil
2011-03-23 2:12 ` Dodji Seketeli
2011-03-28 12:35 ` Jan Kratochvil
2011-04-01 21:03 ` [patch] DWARF-3+ DW_AT_accessibility defaults #3 " Jan Kratochvil
2011-04-03 16:28 ` Jan Kratochvil
2011-04-09 11:21 ` [commit]+[brach commit] " Jan Kratochvil
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=20110321201005.GA922@host1.jankratochvil.net \
--to=jan.kratochvil@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