public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tejohnson at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/55051] [4.8 Regression] profiledbootstrap failed Date: Thu, 15 Nov 2012 01:53:00 -0000 [thread overview] Message-ID: <bug-55051-4-1cjPdW0p3K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55051-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55051 --- Comment #20 from Teresa Johnson <tejohnson at google dot com> 2012-11-15 01:52:45 UTC --- On Wed, Nov 14, 2012 at 5:42 PM, hubicka at ucw dot cz <gcc-bugzilla@gcc.gnu.org> wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55051 > > --- Comment #19 from Jan Hubicka <hubicka at ucw dot cz> 2012-11-15 01:42:55 UTC --- >> Oh got it - it is this one, right?: >> >> profiling:/home/tejohnson/extra/gcc_trunk_3_obj/libcpp/files.gcda:Invocation >> mismatch - some data files may have been removed > > Yes, it is this one. >> >> I think this one was there before, but I had to modify it after my >> histogram change. I will take a look. > > Also could you please make a patch to make maybe_hot_count_p to use > hitogram driven cutoff? Otherwise the histograms would be completely > unused for 4.8 and it would be stupid to carry all the extra data > for no use. I would like this to be done soon, since I plan to base > some of inliner re-tunning to be based on this. Ok, I can do that. I had tried that but didn't see any gain yet (need to take a look at my results again). I have been playing with teasing apart the various uses of this cutoff (inlining vs instruction selection vs etc) too, but can do that in a later release once the appropriate individual cutoffs are tuned. I also have a loop unroller patch on the google branch that uses this that needs to be ported to trunk. It was in the original working set patch I sent for review, that ended up being split out and revised heavily. Shall I resubmit this part for 4.8 or is it too late? Thanks, Teresa > > The mismatch is independent problem, yes. > > Honza > > -- > Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. -- Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413
next prev parent reply other threads:[~2012-11-15 1:53 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-24 10:22 [Bug bootstrap/55051] New: " hjl.tools at gmail dot com 2012-10-24 10:22 ` [Bug bootstrap/55051] " hjl.tools at gmail dot com 2012-10-24 23:50 ` hjl.tools at gmail dot com 2012-10-25 0:49 ` hjl.tools at gmail dot com 2012-10-25 6:52 ` ubizjak at gmail dot com 2012-11-14 15:07 ` hjl.tools at gmail dot com 2012-11-14 15:09 ` hjl.tools at gmail dot com 2012-11-14 15:13 ` markus at trippelsdorf dot de 2012-11-14 15:35 ` hubicka at ucw dot cz 2012-11-14 20:48 ` markus at trippelsdorf dot de 2012-11-14 23:03 ` hubicka at gcc dot gnu.org 2012-11-15 0:07 ` hubicka at gcc dot gnu.org 2012-11-15 0:22 ` tejohnson at google dot com 2012-11-15 0:31 ` hjl.tools at gmail dot com 2012-11-15 1:03 ` hubicka at gcc dot gnu.org 2012-11-15 1:07 ` hubicka at gcc dot gnu.org 2012-11-15 1:10 ` hubicka at gcc dot gnu.org 2012-11-15 1:18 ` hubicka at gcc dot gnu.org 2012-11-15 1:29 ` tejohnson at google dot com 2012-11-15 1:34 ` tejohnson at google dot com 2012-11-15 1:42 ` Jan Hubicka 2012-11-15 1:43 ` hubicka at ucw dot cz 2012-11-15 1:53 ` tejohnson at google dot com [this message] 2012-11-15 2:02 ` hubicka at ucw dot cz 2012-11-15 2:46 ` tejohnson at google dot com 2012-11-15 6:44 ` tejohnson at google dot com 2012-11-15 10:56 ` Jan Hubicka 2012-11-15 10:57 ` hubicka at ucw dot cz 2012-11-15 14:34 ` tejohnson at google dot com 2012-11-15 22:42 ` tejohnson at google dot com 2012-11-16 17:42 ` hubicka at gcc dot gnu.org 2012-11-16 18:03 ` tejohnson at google dot com 2012-11-16 18:57 ` hubicka at ucw dot cz 2012-11-19 5:21 ` tejohnson at gcc dot gnu.org 2012-12-07 12:04 ` rguenth at gcc dot gnu.org
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=bug-55051-4-1cjPdW0p3K@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).