From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] [patch 2/2] Support gcc-4.7 DW_OP_GNU_parameter_ref
Date: Sun, 17 Jun 2012 19:54:00 -0000 [thread overview]
Message-ID: <20120617195424.GB5907@host2.jankratochvil.net> (raw)
In-Reply-To: <87395ws62f.fsf@fleche.redhat.com>
On Fri, 15 Jun 2012 21:55:52 +0200, Tom Tromey wrote:
> I skimmed these patches and nothing weird stood out.
> I can't claim to really understand this extension though.
I find the functionality clear so if there are no typo-crashers checked it in:
http://sourceware.org/ml/gdb-cvs/2012-06/msg00133.html
Thanks,
Jan
prev parent reply other threads:[~2012-06-17 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 6:49 Jan Kratochvil
2012-06-14 7:23 ` Jan Kratochvil
2012-06-14 9:38 ` Mark Kettenis
2012-06-14 10:21 ` Jan Kratochvil
2012-06-15 19:56 ` Tom Tromey
2012-06-17 19:54 ` Jan Kratochvil [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=20120617195424.GB5907@host2.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