From: Jan Hubicka <hubicka@ucw.cz>
To: Teresa Johnson <tejohnson@google.com>
Cc: Jan Hubicka <hubicka@ucw.cz>,
reply@codereview.appspotmail.com,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Stream profile summary histogram through LTO files (issue6782131)
Date: Thu, 29 Nov 2012 16:55:00 -0000 [thread overview]
Message-ID: <20121129165500.GC25651@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAAe5K+Xx=0E9biqpYcC-Ep7uaNKZFXJNzeUMHfDbaEJPKG+MrQ@mail.gmail.com>
>
> I assume you mean use the bitpack streaming functionality used other
> places in lto-cgraph.c, and not change the way it is done in gcov-io.c
> where this was cloned from? I will change the lto-cgraph.c code to use
> the bitpacking.
Yes, we don't have the facility on gcov-io, so we need to do that by hand.
>
> >> + lto_gcov_summary.sum_all = MAX (lto_gcov_summary.sum_all,
> >> + (file_data->profile_info.sum_all
> >> + * scale
> >> + + REG_BR_PROB_BASE / 2)
> >> + / REG_BR_PROB_BASE);
> >
> > Use RDIV for the scaling.
>
> ok. This was cloned from the way we do other scalings in the same
> function, I will change them all to use RDIV.
Yes, thanks!
>
> >> -#if IN_LIBGCOV || !IN_GCOV
> >> +#if !IN_GCOV
> >> /* Determine the index into histogram for VALUE. */
> >>
> >> -static unsigned
> >> +GCOV_LINKAGE unsigned
> > I would probably go around the trouble of declaring this static in GCOV,
> > so it is inlined at we do not bload libgcov more than needed.
>
> Do you mean leave it static when IN_LIBGCOV? It isn't included when
> IN_GCOV. I just need it extern when in the compiler. So do you mean
> make it static when IN_LIBGCOV and GCOV_LINKAGE (i.e. extern) when
> !IN_LIBGCOV?
Yes, it should help inliner to do the right things for libgcov...
Thanks,
Honza
>
> Thanks,
> Teresa
>
> >
> > Thanks,
> > Honza
>
>
>
> --
> Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413
next prev parent reply other threads:[~2012-11-29 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 4:11 Teresa Johnson
2012-11-29 16:17 ` Jan Hubicka
2012-11-29 16:46 ` Teresa Johnson
2012-11-29 16:55 ` Jan Hubicka [this message]
2012-11-30 15:11 Teresa Johnson
2012-11-30 16:17 ` Jan Hubicka
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=20121129165500.GC25651@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=reply@codereview.appspotmail.com \
--cc=tejohnson@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).