From: Xinliang David Li <davidxl@google.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: another gcov cleanup
Date: Sat, 26 Jul 2014 17:01:00 -0000 [thread overview]
Message-ID: <CAAkRFZ+1MiZm7mb_CCb1MZ8_Jbfnr7buj+0+bKwFW8f2LTZUxQ@mail.gmail.com> (raw)
In-Reply-To: <53D353DB.6060707@acm.org>
looks good. thanks.
David
On Sat, Jul 26, 2014 at 12:08 AM, Nathan Sidwell <nathan@acm.org> wrote:
> This patch removes 2 global variables -- gi_filename and gcov_max_filename.
> The relevant data is moved into the renamed gcov_filename structure and
> length is calculated later in the process.
>
> One more change and then David's required support for triggering dumping
> across shared objects will essentially fall out.
>
> nathan
prev parent reply other threads:[~2014-07-26 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 7:33 Nathan Sidwell
2014-07-26 17:01 ` Xinliang David Li [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=CAAkRFZ+1MiZm7mb_CCb1MZ8_Jbfnr7buj+0+bKwFW8f2LTZUxQ@mail.gmail.com \
--to=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.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).