From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] py-value.exp: Use different names for C/C++ .o files.
Date: Wed, 07 Aug 2013 15:15:00 -0000 [thread overview]
Message-ID: <20130807151501.GA2837@host2.jankratochvil.net> (raw)
In-Reply-To: <yjt2d2px3yod.fsf@ruffy.mtv.corp.google.com>
On Thu, 01 Aug 2013 23:10:10 +0200, Doug Evans wrote:
> While I was at it I renamed py-value.cc which is used by py-value-cc.exp.
> It's confusing to have py-value.cc *not* used by py-value.exp.
This is BTW an unrelated part of the patch (I do not mind).
> Regression tested on amd64-linux, with/without Fission.
I wanted to look at the Fission behavior but I cannot Google out where to find
/usr/bin/dwp . Could you reference in contrib/cc-with-tweaks.sh and/or DWP
Wiki where to get the dwp tool?
Thanks,
Jan
next prev parent reply other threads:[~2013-08-07 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 21:10 Doug Evans
2013-08-07 15:15 ` Jan Kratochvil [this message]
2013-08-07 16:49 ` Cary Coutant
2013-08-07 17:12 ` Cary Coutant
2013-08-07 19:11 ` 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=20130807151501.GA2837@host2.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).